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

HTTP Trigger Trows HTTP 404 Error

Hi,

I have an http triggered application on a CRS 3.0.3 server, this application is working fine with a trigger like this "http://10.1.1.1:8080/greeting" with a Call Manager 3.2.

Reciently i moved this application to a CRS 3.0.3 connected to a Call Manager 3.3 but it shows me a 404 error.

Do you know if something changed to the http trigger setup structure or if it need to setup something else on the CRS?

I must say that this sistems are as coresident.

I'll apreciate any help.

Thank you.

  • Other Collaboration Voice and Video Subjects
1 ACCEPTED SOLUTION

Accepted Solutions
Bronze

Re: HTTP Trigger Trows HTTP 404 Error

Hi,

Symptom: The HTTP subsystem does not come in service on a co-resident system

Solution: If Cisco CRA 3.0(3) and Cisco CallManager 3.3(2) are installed on the same server, the HTTP subsystem may not come into service because of a port conflict.

To work around this problem, follow these steps:

1. Make a backup of the server.xml configuration file. This file is stored in the \tomcat\conf\ directory under the directory in which you installed Cisco CRA.

2. Use a text editor to open the original server.xml file.

3. Search the file for the string "Normal HTTP".

4. Look below this string for a line similar to the following:

value="8080"

5. Change the value 8080 to another value (for example, 8081).

6. Save the configuration file.

7. Stop and then restart the CRA Engine.

This is documented in the CRA 3.0(3a) Release notes,

http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/apps_3_0/english/admn_app/relnote/rel3_0_3.htm#1102614

Regards

Venkat

2 REPLIES
Bronze

Re: HTTP Trigger Trows HTTP 404 Error

Hi,

Symptom: The HTTP subsystem does not come in service on a co-resident system

Solution: If Cisco CRA 3.0(3) and Cisco CallManager 3.3(2) are installed on the same server, the HTTP subsystem may not come into service because of a port conflict.

To work around this problem, follow these steps:

1. Make a backup of the server.xml configuration file. This file is stored in the \tomcat\conf\ directory under the directory in which you installed Cisco CRA.

2. Use a text editor to open the original server.xml file.

3. Search the file for the string "Normal HTTP".

4. Look below this string for a line similar to the following:

value="8080"

5. Change the value 8080 to another value (for example, 8081).

6. Save the configuration file.

7. Stop and then restart the CRA Engine.

This is documented in the CRA 3.0(3a) Release notes,

http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/apps_3_0/english/admn_app/relnote/rel3_0_3.htm#1102614

Regards

Venkat

New Member

Re: HTTP Trigger Trows HTTP 404 Error

Thank you a lot Venkat, this helped me to solve my problem. now i could have my test environment complete.

Thank you.

295
Views
0
Helpful
2
Replies
This widget could not be displayed.