[OpenSIPS-Users] opensipsctl dispatcher - show and dump

[Bogdan Andrei IANCU]

Thank you Diptesh,You may be right, only the holy manual knows eveything ;).Regards, BogdanSent from my Samsung Galaxy smartphone.
-------- Original message --------From: Dipteshkumar Patel <diptesh.patel at ecosmob.com> Date: 1/4/20  19:27  (GMT+02:00) To: OpenSIPS users mailling list <users at lists.opensips.org> Subject: Re: [OpenSIPS-Users] opensipsctl dispatcher - show and dump Hello Bogdan,I want to correct you.  The `dump` cmd gives the data from OpenSIPS memory  (via MI), while the `show` gives the data from DB. Am I right?Don't mind, you know OpensSIPS better than me :).Thanks & RegardsDiptesh PatelSoftware Developer Ecosmob Technologies Ltd, AhmedabadMo:+919898962659On Sat, Jan 4, 2020 at 9:17 PM Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:
  
    
  
  
    Hi,
      
      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
https://opensips.org/html/docs/modules/2.4.x/dispatcher.html#param_persistent_state).
      
      Best regards,
    
    Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
  https://www.opensips.org/events/Summit-2020Amsterdam/
OpenSIPS Bootcamp, Miami, March 2020
  https://opensips.org/training/OpenSIPS_Bootcamp_2020/


    On 12/18/19 10:10 AM, solarmon wrote:
    
    
      
        Hi,
        
        
        A question about the opensipsctl dispatcher show and dump
          commands. They seem to show different 'state' for each
          endpoint.
        
        
        For example:
          
          
          When using "opensipsctl dispatcher show":
            
+----+-------+------------------------+-----------------------+-------+--------+----------+-------+--------------+
            | id | setid | destination            | socket              
             | state | weight | priority | attrs | description  |
+----+-------+------------------------+-----------------------+-------+--------+----------+-------+--------------+
            |  1 |     1 | sip:A.B.C.D:5060   | udp:W.X.Y.Z:5060 |     2
            | 1      |        0 |       | |
            
            When using "opensipsctl dispatcher dump":
            
                    SET:: 1
                            URI:: sip:A.B.C.D:5060 state=Active
            first_hit_counter=0
                                    socket:: udp:W.X.Y.Z:5060
          
        
        
        
        
        
        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".
        
        
        
        On the OpenSIPS Control Panel web GUI, it shows it as DB
          State as Active and Memory State as green dot (for Active).
        
        
        Why does  "opensipsctl dispatcher show" has the state as
          "2" for Probing instead of "0" for Active?
        
        
      
      
      
      _______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

    
    
  

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



DisclaimerIn 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.ConfidentialityThis 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.Caution for viruses, malware etc.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. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200104/887a75fb/attachment-0001.html>