com.github.Baresip
com.github.Baresip
com.github.Baresip
invoke
(IN s command, OUT s response);
<h1>Signals</h1>
event
(s class, s evtype, s param);
message
(s ua, s peer, s ctype, s body);
<h1>Description</h1>
<p>This DBus interface supports invoking of baresip commands and sends UA Events as DBus signal.</p>
<h1>Method Details</h1>
<h2>The invoke() method</h2>
com.github.Baresip.invoke()
<pre><code>invoke (IN  s command,
        OUT s response);</code></pre>
<p>Invokes a baresip command which can be a single character command or a long command with appended parameters. Use a blank to separate the command from its parameters! Multiple parameters are often separated by commas. But this depends on the implementation of the command.</p>
<dl>
<dt><code>IN s </code>:</dt>
<dd><p>The command to be executed with appended parameters.</p>
</dd>
<dt><code>OUT s </code>:</dt>
<dd><p>The output of the command.</p>
</dd>
</dl>
<h1>Signal Details</h1>
<h2>The &quot;event&quot; signal</h2>
com.github.Baresip::event
<pre><code>event (s class,
       s evtype,
       s param);</code></pre>
<dl>
<dt><code>s </code>:</dt>
<dd><p>The UA event class.</p>
</dd>
<dt><code>s </code>:</dt>
<dd><p>The UA event type.</p>
</dd>
<dt><code>s </code>:</dt>
<dd><p>The whole event as JSON object including additional parameters.</p>
</dd>
</dl>
<h2>The &quot;message&quot; signal</h2>
com.github.Baresip::message
<pre><code>message (s ua,
         s peer,
         s ctype,
         s body);</code></pre>
<dl>
<dt><code>s </code>:</dt>
<dd><p>User-Agent local SIP URI (aor)</p>
</dd>
<dt><code>s </code>:</dt>
<dd><p>Peer address URI</p>
</dd>
<dt><code>s </code>:</dt>
<dd><p>Content type (&quot;text/plain&quot;)</p>
</dd>
<dt><code>s </code>:</dt>
<dd><p>SIP message body</p>
</dd>
</dl>