HTTP trigger fails with a 404 error message

Unanswered Question

Hello All,

I am in the process of building a UCCX 7.0 HA cluster in parallel to the existing IPCCX 4.0 HA cluster. Everything has gone good so far until we got to the point of testing the HTTP triggers. We have a web page that we access on the servers that are used to update an XML file that is then parsed by other scripts that look to see if the contact center is in an emergency state. Accessing the web page is fine and so is selcting emergency mode or not. The issue comes up when we go to press the Apply button and get the 404 error. The apply button is a link to the HTTP trigger (in this case http://ip of the UCCX server:8080/XMLUpload2) and when pressed it immediately comes back with the 404 error (screenshot attached) on the new server.

On the old server it works just fine. The script is pretty simple (screenshot attached) and the only difference between the application in the new UCCX server is the variable for the username used by the GetUser step. In the old system the CCM was using DC Directory while the new CCM cluster is integrated with AD. Therefore instead of using the "crsadmin" username that had been created for the old system I am using a username that is configured as a test agent, administrator, and supervisor within UCCX. Not sure if this would cause the problem but it seems like a suspect. Any idea what might be causing this issue because I'm a bit stumped at this point. Thanks in advance for the help.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Tanner Ezell Mon, 02/22/2010 - 12:51
User Badges:
  • Silver, 250 points or more

That's certainly interesting, curious, have you applied any SR's (the latest being SR5) to your UCCX?

Abdulbaseer Mohammed Mon, 02/22/2010 - 22:14
User Badges:
  • Silver, 250 points or more

Looks like very simple issue.

My suggestion is try the same commands from any other browser and see what happens.  Make sure you use same user ID's etc to get to the page.

Can't seem to see your CRS code image clear.

Good luck.

It was tested from multiple broswers and PCs. The user IDs were different because we are now integrated with AD instead of DCD in the old cluster and the old user ID doesn't exist in AD.

Got it figured out finally. It was an extra step that is now needed. Now you have to use the AuthenticateUser step after you use the GetUser step. Once we did that it worked as planned.

Gabriel Saavedra Tue, 02/23/2010 - 14:51
User Badges:
  • Silver, 250 points or more

Hi Shan,

what happens if you try using a different script with the same http trigger...try to send a variable to the script and that the script sends back an http response...does it shows the same 404 error message?



This Discussion