I've been experimenting with a HTTP contact today; but it's not working quite as I would expect.
Basically I take a HTTP contact in, and build a response which I then send using a 'send HTTP response' step. My understanding was that as soon as this step is executed the response would be sent back to the browser/web site making the HTTP call.
What actually seems to happen is that when this step is hit, the browser is still awaiting a response. When the script reaches the 'end' step, it actually sends the response... I have things happening in my script after the response should be sent, so don't want the browser to block until the script ends.
Oddly, if I fire up Wireshark I see the data in a packet sent when I hit the 'send http response' step; and again at the end of the script. The first packet isn't interpreted as text/xml, but the second one is....
Anyone seen this sort of thing?
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...