The CUCiMOC now logs in and gives all green status. When a call is made from a desk phone the corresponding desk phone and CUCiMOC ring and both can answer with two way voice.
2 outstanding issues
When selecting desk phone or trying to dial from CUCiMOC in deskphone mode I get the error:
"Failed to start a conversation
A Problem occurred with the JTAPI software library that controls your desk phone"
When trying to dial, the desk phone picks upand give the fast busy error sound.
However the desk phone does appear to be "paired" since CUCiMOC alerts when off hock or if a call is in progress.
Both CUCiMOC's can receive calls (when dialled from a desk phone) and get two way audio, but neither can dial 4 digit extensions, they just give the busy signal.
I have the following setup
User1 Bill Gates, AD\OCS number +441582422001
Their physical phone DN is 2001
User2: John Chambers with the setup with +441582422001 and 2001 on CUCM
This translation pattern, 44158242.200X, allows CUCiMOC to dial with "441582422000" and successfully make a call to the 200 desk phone or CUCiMOC, but not the +44 number you get if you drop the contact on the phone icon. I am not convinced this is the correct way to set it up?
But I still can't get CUCiMOC to successfully call a 4 digit extension
Well I'm experiencing the same issue,when looking into the CFS log I can see that the calledParty field is empty altough CUCIMOC is able to display the number details of my contact persons as per screenshot below
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.