[OpenSIPS-Users] Dispatcher issue in Active -> Probing State.

Bogdan-Andrei Iancu bogdan at opensips.org
Mon May 2 14:05:04 UTC 2022


Do you use the default threshold value ? Also, have you enabled log 
level 4 (debug) and locate the log line for the probing part, to 
understand OpenSIPS behavior upon probing ?


Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
OpenSIPS eBootcamp 23rd May - 3rd June 2022

On 4/22/22 11:15 AM, Vinayak Makwana via Users wrote:
> Hi all,
>          I having issue with dispatcher module in that when i execute 
> "opensipsctl dispatcher dump" command at that time i am getting like this
> "URI:: sip: <> state=Active 
> first_hit_counter=0"     but the trunk doesn't respond to the OPTIONS 
> packet and it needs to change state from Active to probing as per 
> below configuration but it doesn't work.
> Why does it not get into probing state after ds_ping_interval timeout 
> and ds_probing_threshhold reached?
> I am using OpenSIPS Version : 2.4.11
> Here's my configuration for dispatcher module
> loadmodule "dispatcher.so"
> modparam("dispatcher","db_url","URL")
> modparam("dispatcher", "ds_ping_from", "sip:opensips at pinger.com 
> <mailto:sip%3Aopensips at pinger.com>")
> modparam("dispatcher", "ds_ping_interval", 30)
> modparam("dispatcher", "ds_probing_sock", "udp: 
> <>")
> modparam("dispatcher", "ds_probing_mode", 1)
> modparam("dispatcher", "persistent_state", 1)
> Please Provide any suggestion regarding this
> Regards
> Vinayak Makwana
> *Disclaimer*
> 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.
> *Confidentiality*
> 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.
> *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.
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220502/e875c3d1/attachment.html>

More information about the Users mailing list