[cisco-voip] HTTP Response for HTTP Triggered Script
Tanner Ezell
tanner.ezell at gmail.com
Tue Jan 28 10:26:42 EST 2020
This is normal and expected behavior. Use the HTTP trigger app to catch the
request, use Trigger Application step, and sessions to pass success
failure, then end the http trigged app. That'll do the request. Good luck
On Tue, Jan 28, 2020 at 6:15 AM Johnson, Tim <johns10t at cmich.edu> wrote:
> As far as my experience, this is “normal” for UCCX. Yes, I believe the
> request stays open until the script ends. I believe we opened up a TAC case
> about it a year or two ago but I don’t believe it went anywhere.
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Matthew
> Loraditch
> *Sent:* Tuesday, January 28, 2020 8:06 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] HTTP Response for HTTP Triggered Script
>
>
>
> Got the following comment from the developer who is writing an app that
> will queue a call via http trigger:
>
> *It seems like the MobileApp integration is accepting my request, spits
> back some HTML, but the HTTP request remains open until the queued call is
> answered.*
>
>
>
> *Ideally, that HTTP request would be closed with a successful HTTP status
> code (e.g. HTTP 200) when the call was queued, so that I can report back to
> the user that they can wait for a callback. *
>
>
>
> I understand his problem, but I see no way of fixing it. The send http
> response command doesn’t seem to have any settings but the doc sent back.
> Is this normal behavior or can I do something with the doc being sent back
> to make it work?
>
>
>
>
>
> *Matthew Loraditch***
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
> |
>
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
>
> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200128/b724747b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200128/b724747b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200128/b724747b/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200128/b724747b/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 19523 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200128/b724747b/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6884 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200128/b724747b/attachment-0003.png>
More information about the cisco-voip
mailing list