I've spent countless hours over the past few months, off and on, trying to get Jabber Guest working. Finally, after a 5 hour call with TAC, i've got it working to devices that are registered with the VCS-C and life is good.
However, never one to be complacent, I'd like to extend Jabber Guest to be able to dial directly to my SIP URI on my Jabber for Win client. It seems, I'm missing some config that will connect the two systems (VCS -> CUCM/CUPS/J4WIN) and make it work as VCS is not able to locate my URI.
I'm hoping someone can provide some direction (documentation, pointers, etc.) to help me finish this up.
URI dialing does work within my organization (audio only, no video for some reason, still need to figure that out as well) from J4Win to J4Win.
Are you able to dial from the VCS-C registered endpoints to CUCM using SIP URI? If not look into that first, CSS on the VCS-C SIP Trunk, etc then look at Jabber Guest side are you also using TCP or TLS as the VCS to CUCM SIP Trunk?
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.