XML response not understood by sipgate.io's server

[danielberlin]

Testing the provided reject.php (from examples) on my server with curl and a certain combination of from and to parameters, I get:

HTTP/1.1 200 OK
Date: [...] GMT
Server: Apache/2.2
Content-Length: 84
Content-Type: application/xml

[XML output here which is not shown in github's comment for unknown reason]

I noticed that the provided reject.php produces an XML output slightly different from that one shown on the documentation (https://github.com/sipgate/sipgate.io) where under "Example 2" the keyword "busy" is followed by a space before the terminating slash where there is no space in reject.php's output between "busy" and the slash.

Having a look in the log on the dashboard for a request generated in real with the same from and to numbers as the curl request above, I get:

500 - Internal Server Error
Request:
from=491234567&to=49876543
Response:
Socket is closed

However, the exactly same request which the dashboard log declares as 500 is logged as 200 on my web server:

push-api.sipgate.net - - [...] "POST /path/reject.php HTTP/1.1" 401 1411 "-" "sipgate.io"
push-api.sipgate.net - authuser [...] "POST /path/reject.php HTTP/1.1" 200 84 "-" "sipgate.io"

Any manual curl testing never produces an 500 Internal Server Error, I always get my application/xml output with a HTTP 200 response.

What can I do for further debugging?

[TheCK]

Thanks for opening the issue. We'll have a look into it first thing in the morning.

[ghost]

Can confirm this. Have the same issue here

[tpxtron]

Strange. I just tested the PHP example script on my vServer running PHP 5.4.33-1~dotdeb.0 as CGI module within a Lighttpd web server, and it worked fine.
What PHP versions are you guys using?

[ghost]

I'm using Apache 2.2.16 with PHP Version 5.3.3-7+squeeze22

I'm using a script to send me a mail, if the callers number has a bad rating in tellows.
I can receive the mails. So the script is working.
If I open the URL in my browser I will see the result, so this is working without problems

[TheCK]

could you retry with with your script? This should be fixed now.

[ghost]

Yes, now it works! Thanks :)

[danielberlin]

Now also working very well for me, no more Internal Server Error. Thanks for quick fix!