CAXL Sign in failure

RE: CAXL Sign in failure

2013-02-06T20:21:09Z

Hi Allan, Good question, my understanding is the publisher should be good enough. Isn't that the case for you? The 7 servers are cucm or cup? Howard

RE: CAXL Sign in failure

2013-01-25T23:54:42Z

I was able to get it to connect by changing the httpbinding from our normal login name to the actual node name directly. an nslookup of the normal login name provides the IP's for each of the 7 servers in our cluster. is there a way we can check for login against each cluster or should only the publisher be used. Thx, Allan Haigh

RE: CAXL Sign in failure

2013-01-25T23:48:24Z

I have checked to ensure the domain name matches and they do. In the config i placed above I edited it to show domain.ca for confidentiality reasons. Allan

RE: CAXL Sign in failure

2013-01-25T23:08:23Z

Allan, Can you check if the domain name match with the setting on CUP? Howard

RE: CAXL Sign in failure

2013-01-25T22:54:07Z

Hello Howard, The service you mentioned is already running and presistent chat external databases are already configured as well. We are currently using CUPC within the company on the same CUP servers and are able to see chat logs etc. I have full access to the solution as i'm one of the sys admins. I have also confirmed we are using the correct conference alias. Any other ideas?

RE: CAXL Sign in failure

2013-01-25T20:36:16Z

Hi Allan, Do you have access to the CUP server? Please check if the "Cisco XCP Text Conference Manager" is running. If not, please start this service Before you start "Cisco XCP Text Conference Manager", make sure that you have either persistent chat setup with exteral database or disable the persistent chat. Once the service is up, everything should work Let me know if you have any question. Thanks, Howard

CAXL Sign in failure

2013-01-25T19:20:21Z

Hello, I am trying to deploy a CAXL client in our environment, we are running an on-prem CUP environment. I have successfully logged in using my lab environement when trying to connect to my production environement i get the following error.

Log	12:02:27:072	Note: Service discovery is disabled on the client.
Log	12:02:27:075	Update _connectToNode = httpbinding_prod
Log	12:02:27:078	Bosh URL is: [url=http://webserver/httpbinding_prod]http://webserver/httpbinding_prod[/url]
Log	12:02:27:119	[Console] Stream opened with sjrb.ca PLAINCISCO-VTG-TOKEN[i]servername[/i]nodeaname-02
Sent	12:02:27:134	AGFoYWlnaDEAUmVmaWN1bDQ=
Log	12:02:27:155	network timeout retry 1
Log	12:02:27:660	network timeout retry 2
Log	12:02:28:192	network timeout retry 3
Log	12:02:28:738	[Console] Stream closed with error: Operation failed ()
Log	12:02:28:744	closed:

This is running on a nginx webserver. Configurations are as follows. location /httpbinding_prod { access_log off; proxy_pass [url=http://servergroupname.domain:7335/httpbinding]http://servergroupname.domain:7335/httpbinding[/url]; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } var demo_config = { domain: "domain.ca", maxGraphAge: 5, unsecureAllowed: true, atSymbolAllowed: false, logPersistence: true, conferencealias: "conference-3.", serviceDiscoveryEnabled: false, httpBindingURL: "/httpbinding_prod" }; Cisco UP XCP Connection Manager is running Cisco UP XCP Direcotry Service is running Cisco UP XCP Authentication Service is running. when i goto to the binding URL i do get the proper reponse so i know that is working. Any suggestions on additional cup server configurations that are requiered for deployment would be appreciated. Thanks, Allan