[Matt]

I have been seeing a lot of the following errors in my log.

SOAP Error: HTTP Error: socket read of headers timed out

Do you know what might be the cause of this?

[Andrew Gillard]

Since headers are the first thing to be read from an HTTP request, that sounds like a simple remote server timeout - perhaps caused by it being too busy.

[Matt]

I am a little confused and without much knowledge of SOAP I do not know where to start debugging or getting accurate error messages. But I did the var_dump and I get bool(false). However I was doing a page redirect before but with the testing here I did not. This revealed that I have been receiving a 'SOAP Error: HTTP Error: socket read of headers timed out' error all along. The ticket does get submitting almost instantly but the return seems to time out? Everything is on the same server. When I use the call('postTicketReply', $params), this works instantly without any timeout. Also I am using the SOAP API for my knowledge base and that works without timing out.

So is there some issue with the submitTicket function or my parameters? (I am not sure where the call() function is located.)

[Andrew Gillard]

call() is not a standard PHP function, so it must be defined *somewhere*... Without seeing it and how it works, I can only really make vague guesses.

As far as "how SOAP works" goes: it's just a technology that combines XML and HTTP to create a communications protocol. The client sends an XML document (containing the request) to the server as part of a POST request, which reads it and sends an XML document back as the body of the response. I think, at least - my SOAP knowledge isn't particularly high, and thankfully nuSOAP and the PHP SOAP extension abstract the complexity away from me

[Matt]

I used the exact same call() function as you have in your Example Usage.

[Andrew Gillard]

That example function (and the entire example, really) isn't exactly the best way of doing things, what with the fact that it just halts all script execution if there's an error, rather than carrying on but with a warning.

I'm not really sure why it would be giving you bool(false) as the return value, though... :/