UCCX - HTTP Trigger Error

[Tan Jay Sern]

Hello guys,

Need some help here. I am trying to create a HTTP trigger for my scheduled callback script. However I am getting the following error "The requested resource (/ScheduledCallback) is not available" as shown below. Below are my Application and HTTP trigger configuration as weel as the error screenshot.

Please advise where I did wrong, appreciate your help and thanks in advance.

[Samuel Womack]

Use this URL:

http://10.10.1.40:9080/ScheduledCallback

[Tan Jay Sern]

Hello,

Thanks for the reply. I tried

http://10.10.1.40:9080/ScheduledCallback

and i get HTTP 500 Internal server error, the website cannot display the page.

[Samuel Womack · Accepted solution]

What do you think you are going to get back?..unless you program your script to send a Response Back this is actually the Normal Response..if you want to see what's going on with your script that is being "executed" by the Web Trigger then you should set up a Reactive Debug and then hit send in the Browser to your /ScheduleCallBack Trigger..

[Tan Jay Sern]

Thanks, I got it in reactive debug

[collinks2]

Hi,i know this is an old post.I am having the same problem.I can't see anything in the debug once I hit the send button in the browser.
My url in the browser is
http://uccx-ip:8080/webcallback

Update:

I changed the port no to 9089 and I viewed it in the debug

[Anthony Holloway]

Did you try HTTP + Port 9080, or HTTPS and Port 9443 yet?

[collinks2]

I changed it to
http://uccx-ip:9080/webcallback.
I didnt try https on 9443.May be I can try it.
The other challenge I have is that
The debug stopped at "waitforagent" couldn't see the waiting call in the csq. I will figure it out tomorrow

[Anthony Holloway]

Wait, so the HTTP call did trigger the script? Then your issue has nothing to do with this post. You should make your own post.

[collinks2]

My issue had something to do with the post. I created a thread on it and
you sent me a link to download the script repository
I replied but have not responded to it. I have been searching on the web to
know the cause of the http trigger error. Its this thread that made me to
understand that i should change the port from http 8080 to http 9080.
I have solved one phase of the problem. The other one should not be
difficult me. So the solution to this thread helped me cos i was not seeing
anything in the debug to http port 8080 which is in the webcallback.aef

[Anthony Holloway]

Oh I see, yeah, the repo example is from an older version. Now that you know the correct port, we can try to troubleshoot the remainder over on your other thread. I did not see that you replied, but I'll check it.