Call Api should send back proper response for request of updating completed calls #2330
Assignees
Labels
Comments
maria-farooq
pushed a commit
that referenced
this issue
Jul 26, 2017
* master: (36 commits) added the patch #2389 added test cases for deleting/updatig a phonenumber that does not exists #2389 Fixes for testsuite Keep autofill text color to grey instead of black Patch to fix misspelled Sms statusCallback attribute This close #2386 fixed callsid in new recording test dont split instance id from callsid trim callsid value after getting from header fixed hsql scripts fixed hsql script fixed the bug improved logging improved logging updated mysql file updated call-sid column length patched #2330 fixes #2038 change background of login file to white Fixes #2038 remove blue/red border when focusing on textbox at login page Fixes #2038 remove yeloow color in text box of login page added default invalid callSid ... Conflicts: restcomm/restcomm.http/src/main/java/org/restcomm/connect/http/IncomingPhoneNumbersEndpoint.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
right now if we try to update an already completed, restcomm responds back with HTTP 500.
IMO we should respond with Call Already Completed.
IMO we should use 410 GONE
The text was updated successfully, but these errors were encountered: