Re: [SR-Users] Reactivating a failed dispatcher destination

Hi Daniel, I can see the gateway flagged as P after so many failed attempts but when I bring the server back up I can see the pings being received by the server but Kamailio still has a P against the dispatcher dump. The server is definitely working and pings are getting through. SET:: 443012572 URI:: sip:172.16.7.124:5060 flag=A SET:: 443012571 URI:: sip:172.16.7.122:5060 flag=P SET:: 443012570 URI:: sip:172.16.7.122:5060 flag=P Hi Carsten, I am loading dispatcher after tm. My settings for this are modparam("dispatcher", "flags", 2) modparam("dispatcher", "ds_ping_interval", 10) modparam("dispatcher", "ds_probing_threshhold", 3) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_ping_method", "INFO"). Thanks for help guys. Regards Lee From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: 20 May 2011 09:06 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List Cc: Lee Archer Subject: Re: [SR-Users] Reactivating a failed dispatcher destination On 5/19/11 4:05 PM, Lee Archer wrote: Hi all I wonder if someone can help by pointing me in the right direction. I have dispatcher set to ping and set any failed gateways to probing but how do you get them out of this state when they start working again? I have run some tests and I must be missing something as active servers seem to stay in probing mode. I am using Kamailio 3.0.4. isn't pinging going on even after setting it inactive destination and as soon as it becomes online will mark it active again? Administrative choice is to use mi/rpc command: kamctl fifo ds_set_state ... http://kamailio.org/docs/modules/stable/modules_k/dispatcher.html#id2807 032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda