Subject: RE: chat-proxy problem with CUPS integration
Replied by: James Maudlin on 29-08-2012 12:22:05 PM
What version of WBS are you on?
This document was generated from CDN thread
Created by: Daniele Salladini on 29-08-2012 11:21:22 AM
Hi team,
i have new trouble with CUPS chat integration.
In first time CUPS working well (i explain in other topic). Then i tried to configure webex IM without success (i have a ticket opened with TAC), and now i would to came back to my CUPS 8.6.4 server (no settings changed), but now it doesn't work giving me error shown in attached "proxyerror.jpg".
Some considerations:
Appserver logs doesn't show anything interesting (which kind of logs must improve for chat logging?)
Sniffing between Appserver and CUPS i see traffic: appserver try to connect with CUPS, beging TCP connection, but after sending first configuration data CUPS don't response back.
Node name of CUPS node is FQDN (how explained on admin guide)
All other parameters on CUPS and WES are right, verified some times!
If i try to connect to CUPS with Jabber client it works well, so i think problem is in WES side.
i have a dubt about configuration in /etc/httpd/conf.d/portal.conf about RewriteRule for chat-proxy; this is my line:
RewriteRule ^/chat-proxy(.*) http://presence.domain:7335/httpbinding$1 (presence.domain is not real name, but)
It is right?
someone can check on a working integrations if it is in same form?
Any other suggestion?
Thanks,
daniele
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Daniele Salladini on 30-08-2012 03:18:07 AM
Release is 3.0 SR1,
thanks,
Daniele
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Daniele Salladini on 30-08-2012 06:14:48 AM
If can help you, these are logs from appserver_httpd_error log file
[client 138.132.28.190] (104)Connection reset by peer: proxy: error reading status line from remote server presence.domain.com, referer: http://wes.domain.com/html/js/com/cisco/ecp/chat/integrations/jabber/jabberwerx/jabberwerxChat.html?cacheBust=1344041632000
Aug 30 08:14:27 weshostname httpd[1920]: [client 138.132.28.190] proxy: Error reading from remote server returned by /chat-proxy, referer: http://wes.domain.com/html/js/com/cisco/ecp/chat/integrations/jabber/jabberwerx/jabberwerxChat.html?cacheBust=1344041632000
thanks,
Daniele
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Daniele Salladini on 31-08-2012 09:43:27 AM
Suggestions?
D
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Sergey Svishenko on 24-09-2012 05:49:58 AM
Hello!
I have the issue with CUP and WES 3.0 SR2 integration.
1) I don't understand what's mean "chat password"
2) User presence status between cisco jabber client and user WES home page don't synchronize.
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Sergey Svishenko on 09-10-2012 04:45:24 AM
Hello Daniele!
I try to integrate WBXS 3.0 SR3 and CUP 8.6.4, could you answer me on some questions:
Do you know what is "chat password"?
Should I use http or https in ://CUP_FQDN:7335/httpbinding URL?
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Daniele Salladini on 09-10-2012 08:51:45 AM
Chat Password is password of your account on CUPS, that generally is the same of CUC ---> Active Directory (if is integrated with it)
for chat proxy binding url use HTTPS
Subject: RE: chat-proxy problem with CUPS integration
Replied by: Sergey Svishenko on 09-10-2012 08:58:01 AM
AD user password don't conform, but with this password my user can successfully login to CUP server CCMUSER page
