<div dir="ltr">Hello Bogdan,<div><br></div><div>I want to correct you. </div><div> <span style="font-family:monospace">The `dump` cmd gives the data from </span>OpenSIPS memory (via MI)<span style="font-family:monospace">, while the `show` gives the data from DB. Am I right?</span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace">Don't mind, you know OpensSIPS better than me :).</span></div><div><span style="font-family:monospace"><br></span></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div>Thanks & Regards</div><div dir="ltr"><b>Diptesh Patel</b><div>Software Developer </div><div>Ecosmob Technologies Ltd, </div><div>Ahmedabad</div><div>Mo:<b>+919898962659</b></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 4, 2020 at 9:17 PM Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<tt>Hi,<br>
<br>
The `dump` cmd gives you the data from DB, while the `show` gives
you the data from OpenSIPS memory (via MI). And during runtime,
the in-memory status of a destination may change (due pinging or
script/MI disabling), while the DB status is not change (still,
see
<a href="https://opensips.org/html/docs/modules/2.4.x/dispatcher.html#param_persistent_state" target="_blank">https://opensips.org/html/docs/modules/2.4.x/dispatcher.html#param_persistent_state</a>).<br>
<br>
Best regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="https://www.opensips-solutions.com" target="_blank">https://www.opensips-solutions.com</a>
OpenSIPS Summit, Amsterdam, May 2020
<a href="https://www.opensips.org/events/Summit-2020Amsterdam/" target="_blank">https://www.opensips.org/events/Summit-2020Amsterdam/</a>
OpenSIPS Bootcamp, Miami, March 2020
<a href="https://opensips.org/training/OpenSIPS_Bootcamp_2020/" target="_blank">https://opensips.org/training/OpenSIPS_Bootcamp_2020/</a>
</pre>
<div>On 12/18/19 10:10 AM, solarmon wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"> Hi,
<div><br>
</div>
<div>A question about the opensipsctl dispatcher show and dump
commands. They seem to show different 'state' for each
endpoint.</div>
<div><br>
</div>
<div>For example:<br>
<div><br>
</div>
<div>When using "opensipsctl dispatcher show":<br>
<br>
+----+-------+------------------------+-----------------------+-------+--------+----------+-------+--------------+<br>
| id | setid | destination | socket
| state | weight | priority | attrs | description |<br>
+----+-------+------------------------+-----------------------+-------+--------+----------+-------+--------------+<br>
| 1 | 1 | <a>sip:A.B.C.D:5060</a> | udp:W.X.Y.Z:5060 | 2
| 1 | 0 | | |<br>
<br>
When using "opensipsctl dispatcher dump":<br>
<br>
SET:: 1<br>
URI:: <a>sip:A.B.C.D:5060</a> state=Active
first_hit_counter=0<br>
socket:: udp:W.X.Y.Z:5060<br>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Why are the 'state' different? In "opensipsctl dispatcher
show" it says the state is "2", which is for 'Probing' as I
understand it. (and 0 is for "Active"?). But for "opensipsctl
dispatcher dump" it shows it as "Active".<br>
</div>
<div><br>
</div>
<div>On the OpenSIPS Control Panel web GUI, it shows it as DB
State as Active and Memory State as green dot (for Active).</div>
<div><br>
</div>
<div>Why does "opensipsctl dispatcher show" has the state as
"2" for Probing instead of "0" for Active?</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>
<br>
<div><font face="Arial" size="2" style="background-color:white" color="#808080"><b>Disclaimer</b></font></div><div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small">In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded.</span></div></div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small"><br></span></div><div><font face="Arial" size="2" style="background-color:white" color="#808080"><b>Confidentiality</b></font></div><div><font face="Arial" size="2" style="background-color:white" color="#808080">This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error.</font></div><div><font face="Arial" size="2" style="background-color:white" color="#808080"><br></font></div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small"><b>Caution for viruses, malware etc.</b></span></div><div><font face="Arial" size="2" style="background-color:white" color="#808080">This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems. </font></div>