sipgate REST-API - Single Call Event funktioniert nicht

Norbert Fröhler

unread,

Feb 19, 2016, 10:01:43 AM2/19/16

to sipgate API

Ich versuche gerade verzweifelt ein Single Call Event entsprechend dem Beispiel unter http://www.live.sipgate.de/api/rest#userIdeventscallscallId zu generieren. Leider liefert der Aufruf

curl -u USERNAME:PASSWORD https://api.sipgate.net/my/events/calls/{callId}/?version=2.41.0&complexity=full

bei calls mit <direction>incoming</direction><location>inbox</location>

folgendes Ergebnis:

<html>

<head>

<title>Status page</title>

</head>

<h3>Internal Server Error</h3><p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1">here</a>.<br>

Please continue your visit at our <a href="/">home page</a>.

</p>

</body>

</html>

Der Fehler "10.5.1 500 Internal Server Error" bedeutet: "The server encountered an unexpected condition which prevented it from fulfilling the request."

Dagegen funktionieren der Aufruf bei calls mit <direction>outgoing</direction><location>outbox</location> ohne Probleme!

Sammelaufrufe und

curl -u USERNAME:PASSWORD https://api.sipgate.net/my/events/calls/?version=2.41.0&complexity=full

die Einzelaufrufe für Faxe, SMS und Voicemails (!)

curl -u USERNAME:PASSWORD https://api.sipgate.net/my/events/faxes/{faxId}/?version=2.41.0&complexity=full

curl -u USERNAME:PASSWORD https://api.sipgate.net/my/events/sms/{smsId}/?version=2.41.0&complexity=full

curl -u USERNAME:PASSWORD https://api.sipgate.net/my/events/voicemails/{voicemailId}/?version=2.41.0&complexity=full

funktionieren ebenfalls. Hat jemand eine Idee, woran dies liegen könnte?

micha.m...@gmail.com

unread,

Feb 29, 2016, 9:53:41 AM2/29/16

to sipgate API

Ich habe ein ähnliches Problem beim Senden von SMS:

<h3>Forbidden</h3><p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4">here</a>.

Ich habe den Sipgate-Support angeschrieben.

Schauen wir mal...

Norbert Fröhler

unread,

Mar 2, 2016, 7:02:49 AM3/2/16

to sipga...@googlegroups.com

Laut Mitteilung von Sipgate, liegt ein Bug in der API vor.

--
You received this message because you are subscribed to a topic in the Google Groups "sipgate API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sipgate-api/P5ZGmymh4aY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sipgate-api...@googlegroups.com.
To post to this group, send email to sipga...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipgate-api.
For more options, visit https://groups.google.com/d/optout.

Reply all

Reply to author

Forward