Uploaded image for project: 'FreeSWITCH'
  1. FreeSWITCH
  2. FS-9997

Invalid JSON-RPC Response to an incorrect JSON-RPC Request.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.9
    • Fix Version/s: None
    • Component/s: mod_verto
    • Labels:
      None
    • Environment:
      debian 7
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 7 wheezy
    • Compiler:
      gcc
    • FreeSWITCH GIT Revision:
      FreeSWITCH Version 1.9.0+git~20161117T043926Z~0578331edf~64bit (git 0578331 2016-11-17 04:39:26Z 64bit)
    • GIT Master Revision hash::
      0578331edf0d128cdca4a5f699698ee343759c50

      Description

      When I issue an incorrect JSON-RPC Request, using my homebrew verto implementation (for example with missing CallID field) :
      [{
      "id": 3,
      "jsonrpc": "2.0",
      "params": {
      "sessid": "f73dbfa3-9dc3-4ba1-9acd-73f45a447360",
      "dialogParams": {
      }
      },
      "method": "verto.bye"
      }]
      I got an invalid JSON-RPC Response, where field "message" repeated twice:
      [{
      "jsonrpc": "2.0",
      "id": 3,
      "error": {
      "message": "CallID missing",
      "message": "CALL DOES NOT EXIST",
      "code": -32002
      }
      }]

      I guess there should be something like "reason" field instead of a second "message" ?


        Attachments

          Activity

            People

            • Assignee:
              mikej Mike Jerris
              Reporter:
              pavelb Pavel Balashov
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: