Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

404 Not Found - Collab Edge - Jabber - VCS C/E

Hello,

I’ve been working on collab edge for about a month with another co-worker. It’s been a rough road to say the least.  We are getting very close and one of our major issues was the external collab edge SRV record which we fixed a couple days ago.  We have CUCM 9.1.2, VCS C/E X8.1, and Jabber 9.6 (also tested a beta version of 9.7).  When logging in externally, we are getting an error using Jabber for Windows that says:

“Cannot communicate with server”

On the VCS C/E, it appears as though CUCM is sending “404 Not Found” when it’s looking for the CSFxxxx.cnf.xml file. I can log in over the VPN or from a machine locally. I’ve verified I can browse to the CSFxxxx.cnf.xml file and can also download it via TFTP locally or over the VPN. CUCM gets the request for the file...I’ve looked through enough logs to it come in then spit out a 404. Pretty stumped.  Here are some logs.

From VCS-C

2014-03-06T11:23:48-05:00 ame-clw-ec01 traffic_server[30157]: UTCTime=”2014-03-06 16:23:48,817″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Sending Request” Dst-ip=”192.168.12.60″ Dst-port=”6970″ Msg=”GET /CSFxxxx.cnf.xml HTTP/1.1″

2014-03-06T11:23:48-05:00 ame-clw-ec01 traffic_server[30157]: UTCTime=”2014-03-06 16:23:48,817″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Sending Request” Dst-ip=”192.168.12.60″ Dst-port=”6970″

HTTPMSG:

|GET /CSFxxxx.cnf.xml HTTP/1.1

Authorization: xxxxx

Host: CLWLABCUCMPub.aaa.net:6970

Accept: */*

Cookie: JSESSIONIDSSO=DB8712449AD7C5350E7115B646FFF5AA; X-Auth=f6f1f684-3897-4c4b-be0e-352cb321ecaf

User-Agent: Jabber-Win-804

X-Forwarded-For: x.x.x.x, 127.0.0.1

Via: https/1.1 vcs[C0A82B0B] (ATS), http/1.1 vcs[C0A8290B] (ATS)

|

2014-03-06T11:23:48-05:00 ame-clw-ec01 traffic_server[30157]: UTCTime=”2014-03-06 16:23:48,819″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Receive Response” Src-ip=”192.168.12.60″ Src-port=”6970″ Msg=”HTTP/1.1 404 Not Found”

2014-03-06T11:23:48-05:00 ame-clw-ec01 traffic_server[30157]: UTCTime=”2014-03-06 16:23:48,819″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Receive Response” Src-ip=”192.168.12.60″ Src-port=”6970″

HTTPMSG:

|HTTP/1.1 404 Not Found

X-Frame-Options: SAMEORIGIN

Content-Type: text/html;charset=utf-8

Content-Length: 2217

Date: Thu, 06 Mar 2014 16:23:48 GMT

Server:

|

2014-03-06T11:23:48-05:00 ame-clw-ec01 traffic_server[30157]: UTCTime=”2014-03-06 16:23:48,819″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Sending Response” Dst-ip=”127.0.0.1″ Dst-port=”34072″ Msg=”HTTP/1.1 404 Not Found”

2014-03-06T11:23:48-05:00 ame-clw-ec01 traffic_server[30157]: UTCTime=”2014-03-06 16:23:48,820″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Sending Response” Dst-ip=”127.0.0.1″ Dst-port=”34072″

HTTPMSG:

|HTTP/1.1 404 Not Found

X-Frame-Options: SAMEORIGIN

Content-Type: text/html;charset=utf-8

Content-Length: 2217

Date: Thu, 06 Mar 2014 16:23:48 GMT

Server:

Age: 0

Connection: keep-alive

From VCS-E

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,793″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Receive Request” Src-ip=”x.x.x.x” Src-port=”56473″ Msg=”GEThttps:///b3JhbmdlYW1lY29lLmNvbS9odHRwL0NMV0xBQkNVQ01QdWIuZ3RzLm5ldC82OTcw/CSFxxxx.cnf.xmlHTTP/1.1″

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,793″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Receive Request” Src-ip=”x.x.x.x” Src-port=”56473″

HTTPMSG:

|GEThttps:///b3JhbmdlYW1lY29lLmNvbS9odHRwL0NMV0xBQkNVQ01QdWIuZ3RzLm5ldC82OTcw/CSFxxxx.cnf.xmlHTTP/1.1

Authorization: xxxxx

Host: ame-clw-ee01.abc-corp.com:8443

Accept: */*

Cookie: JSESSIONIDSSO=DB8712449AD7C5350E7115B646FFF5AA; X-Auth=f6f1f684-3897-4c4b-be0e-352cb321ecaf

User-Agent: Jabber-Win-804

|

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,794″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Sending Request” Dst-ip=”127.0.0.1″ Dst-port=”31174″ Msg=”GET http://vcs_control.abc-corp.com:8443/b3JhbmdlYW1lY29lLmNvbS9odHRwL0NMV0xBQkNVQ01QdWIuZ3RzLm5ldC82OTcw/CSFxxxx.cnf.xml HTTP/1.1″

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,794″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Sending Request” Dst-ip=”127.0.0.1″ Dst-port=”31174″

HTTPMSG:

|GET http://vcs_control.abc-corp.com:8443/b3JhbmdlYW1lY29lLmNvbS9odHRwL0NMV0xBQkNVQ01QdWIuZ3RzLm5ldC82OTcw/CSFxxxx.cnf.xml HTTP/1.1

Authorization: xxxxx

Host: vcs_control.abc-corp.com:8443

Accept: */*

Cookie: JSESSIONIDSSO=DB8712449AD7C5350E7115B646FFF5AA; X-Auth=f6f1f684-3897-4c4b-be0e-352cb321ecaf

User-Agent: Jabber-Win-804

X-Forwarded-For: x.x.x.x

Via: https/1.1 vcs[C0A82B0B] (ATS)

|

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,820″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Receive Response” Src-ip=”127.0.0.1″ Src-port=”31174″ Msg=”HTTP/1.1 404 Not Found”

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,820″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Receive Response” Src-ip=”127.0.0.1″ Src-port=”31174″

HTTPMSG:

|HTTP/1.1 404 Not Found

X-Frame-Options: SAMEORIGIN

Content-Type: text/html;charset=utf-8

Content-Length: 2217

Date: Thu, 06 Mar 2014 16:23:48 GMT

Server:

Age: 0

Connection: keep-alive

|

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,821″ Module=”network.http.trafficserver” Level=”INFO”: Detail=”Sending Response” Dst-ip=”x.x.x.x” Dst-port=”56473″ Msg=”HTTP/1.1 404 Not Found”

2014-03-06T11:23:48-05:00 ame-clw-ee01 traffic_server[27336]: UTCTime=”2014-03-06 16:23:48,821″ Module=”network.http.trafficserver” Level=”DEBUG”: Detail=”Sending Response” Dst-ip=”x.x.x.x” Dst-port=”56473″

HTTPMSG:

|HTTP/1.1 404 Not Found

X-Frame-Options: SAMEORIGIN

Content-Type: text/html;charset=utf-8

Content-Length: 2217

Date: Thu, 06 Mar 2014 16:23:48 GMT

Server:

Age: 0

Connection: keep-alive

|

From CUCM - one of the tomcat local host access logs:

(disregard timestamps - I pulled the logs separate from the VCS C/E)

So this is the VCS C requesting the config file from CUCM.

[06/Mar/2014:14:24:51 -0500] 192.168.41.11 192.168.41.11 xxxx - 8443 GET /cucm-uds/user/xxxx/devices HTTP/1.1 200 5840 142

[06/Mar/2014:14:24:51 -0500] 192.168.41.11 192.168.41.11 xxxx - 6970 GET /CSFxxxx.cnf.xml HTTP/1.1 404 2217 1

As I mentioned above, I can browse to http://<cucm IP>:6970/CSFxxxx.cnf.xml and it will download the file.

5 REPLIES
Cisco Employee

Can you get a network capture

Can you get a network capture of the working and non-working case using the 'utils network capture' command on the TFTP server? Something like this should do the trick: utils network capture count 10000 size ALL port 6970 file tftp Then grab the file using: file get activelog platform/cli/tftp.cap
New Member

Very good idea.  I just

Very good idea.  I just performed these packet captures and I saw quite a bit when I logged in internally.  The capture from an external log in had zero packets with port 6970.  I did it twice just to make sure.  Oddly enough, VCS still shows a 404 coming back from CUCM and the tomcat logs show the same - the GET CSF.cnf.xml file errors out with a 404.  Seems like there's an issue with the TFTP request from VCS.  

 

 

Cisco Employee

Something doesn't make sense

Something doesn't make sense because if the tomcat logs show the GET, it has to be on the wire. While you are doing the capture, can you look at the tomcat logs and see if you see the request coming in? Might be worth it to turn up the debug level for the TFTP service and see if anything shows up in there too. 

New Member

I had TFTP set to debugging

I had TFTP set to debugging but there's nothing looking for the CSF or the IP of our VCS.  That being said, Tomcat still shows the GET request.

New Member

Fixed the issue by upgrading

Fixed the issue by upgrading C and E to the lastest X8.1 release using Jabber 9.7.  Version 9.6 is still giving an error but I haven't had time to dig into that yet.  Regardless, this is progress!

1129
Views
0
Helpful
5
Replies