<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Adrian,</p>
    <p>In the cases (like 'pua_publish') where there are multiple
      optional parameters that cannot be simply identified by position
      in the array, the 'params' member in the JSON-RPC request should
      be an Object with named parameters.</p>
    <p>As such, you should have:<br>
    </p>
    <p>"params": {</p>
    <p>    "presentity_uri": "<a class="moz-txt-link-freetext"
        href="sip:system@192.168.2.132">sip:system@192.168.2.132</a>",</p>
    <p>    "expires": 3600,</p>
    <p>    [...]</p>
    <p>}</p>
    <p>Regards,<br>
    </p>
    <div class="moz-cite-prefix">On 06.07.2020 22:47, Adrian Fretwell
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:6072b3ac-038b-43bb-95bb-d9a7745b4a67@topgreen.co.uk">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <p>Hello,</p>
      <p>What is the correct way to specify empty parameters in an MI
        call using JSON?</p>
      <p>For example this call to pua_publish has two unused parameters;
        ETag and extra_headers, in the old way they were represented by
        a dot, but if I try that now I get an invalid etag message:</p>
      <p>Pua_publish:</p>
      <p><presentity_uri> <br>
         <expires><br>
         <event package><br>
         <content_type>       - body type if body of a type
        different from default event content-type or . <br>
         <ETag>                    - ETag that publish should
        match or . if no ETag<br>
         <extra_headers>    - extra headers to be added to the
        request or .<br>
         <publish_body>      - may not be present in case of
        update for expire</p>
      <p>Example:</p>
      <p>:pua_publish:fifo_reply<br>
        <a class="moz-txt-link-freetext" href="sip:system@192.168.2.132"
          moz-do-not-send="true">sip:system@192.168.2.132</a><br>
        3600<br>
        presence<br>
        application/pidf+xml<br>
        .<br>
        .<br>
        <?xml version='1.0'?><presence
        xmlns='urn:ietf:params:xml:ns:pidf'
        xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model'... etc.<br>
      </p>
      <p>Would someone point me in the right direction please.<br>
      </p>
      <div class="moz-signature"> <br>
      </div>
      <font face="Verdana, Helvetica, Sans-Serif" color="#000000">Kind
        regards,<br>
        <br>
        Adrian Fretwell<br>
        Sibthorpe<br>
        Nottinghamshire<br>
        UK.<br>
        <br>
      </font><small><small><small> </small></small></small> <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Vlad Patrascu
OpenSIPS Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
  </body>
</html>