We have recently installed and configured Jabber Guest for our customer, using the dual-nic scenario for the deployment.
When we try to call anyone, it loads up fine the Call button and when we hit it we can hear a couple of ringbacks but it doesn´t actually ring the destination number. After this, the browser plugin returns an error:
Message: class java.net.ConnectException:Connection refused Category: 2 (ROAP_EXCEPTION) Code: 0
I tried to restart tomcat and reboot the Jabber Guest server, still no luck.
This could be because the Jabber Guest server is trying to send the SIP invite to the Expressway-E when it should've been sending it to the Expressway-C. The JG server should only send the SIP to the Exp-E in a dual NIC environment. Try changing the "Send SIP to" settings on the Jabber Guest Call Control page to send it to the configured Expressway-C addresses and see if it helps.
We actually are using 2 nics on the Expressway-E and poiting to it in the JG configuration, just like you mention it should.
I can't use the Expressway-C to receive the call in this scenario because the zone between it and JG doesn't come up, probably due to the configuration "Send SIP" which has the FQDN of the Expressway-E.
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.