-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
XML response not understood by sipgate.io's server #6
Comments
Thanks for opening the issue. We'll have a look into it first thing in the morning. |
Can confirm this. Have the same issue here |
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. |
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. |
could you retry with with your script? This should be fixed now. |
Yes, now it works! Thanks :) |
Now also working very well for me, no more Internal Server Error. Thanks for quick fix! |
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?
The text was updated successfully, but these errors were encountered: