anchor.diff:  
   * `method` (required, string). Value: `create`.
   * `params` (required, object). Parameters for the invocation of the create message, containing these members:
  -    * type (required, string). Media element to be created. Allowed Values:
  +    * type (required, string). Media pipeline or media element to be created. The allowed values are the following:
  +        * `MediaPipeline`: Media Pipeline to be created.
           * `WebRtcEndpoint`: This Endpoint offers media streaming using WebRTC.
           * `RtpEndpoint`: Endpoint that provides bidirectional content delivery capabilities with remote networked peers through RTP protocol. It contains paired sink and source MediaPad for audio and video.
           * `HttpPostEndpoint`: This type of Endpoint provide unidirectional communications. Its MediaSource are related to HTTP POST method. It contains sink MediaPad for audio and video, which provide access to an HTTP file upload function.
  
positive.code: A `release` request contains the following parameters:
  
  * `method` (required, string). Value is `release`.
  * `params` (required, object). 
      * `object` (required, number). Identifier of the media element to be released.
          * `sessionId` (required, string). Session identifier.
  
  + Body (application/json)
  
          {
            "jsonrpc": "2.0",
            "id": 3,
            "method": "release",
            "params": {
              "object": "442352747",
              "sessionId": "c93e5bf0-4fd0-4888-9411-765ff5d89b93"
            }
          }
  
  ### Response
  
negative.code: * `id`: an unique identifier established by the client that contains a string or number. The server must reply with the same value in the response message. This member is used to correlate the context between both messages.
  * `method`: a string containing the name of the method to be invoked.
  * `params`: a structured value that holds the parameter values to be used during the invocation of the method.
  
  Therefore, the value of the `method` parameter in the request determines the type of request/response to be exchanged between client and server. The following section describes each pair of messages depending of the type of `method` (namely: `Ping`, `Create`, `Invoke`, `Release`, `Subscribe`, `Unsubscribe`, and `OnEvent`).
  
  When an RPC call is made by a client, the server replies with a response object. In the case of a success, the response object contains the following members:
  
  