Reactivating a failed dispatcher destination

List overview All Threads
Download

newer

older

nonce reuse parameter

packaging 3.1.4

Lee Archer

19 May 2011 19 May '11

5:05 p.m.

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. Thanks Lee

Attachments:

attachment.html (text/html — 1.9 KB)

Show replies by date

Daniel-Constantin Mierla

20 May 20 May

11:05 a.m.

On 5/19/11 4:05 PM, Lee Archer wrote:

...

Hiall I wonder if someone canhelp bypointingme in the right direction. Ihave dispatcher set toping and set any failedgatewaysto probing but how do you get them out ofthis state when they start working again? I have run some tests and Imust bemissing something as active serversseem 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#id2807032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda

Carsten Bock

11:10 a.m.

Hi, is the TM-Module loaded before the dispatcher module? Otherwise, the automatic Pinging is deactivated. Also, please check the Parameters set to the dispatcher module. Kind regards, Carsten 2011/5/20 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:

...

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#id2807032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

Lee Archer

11:38 a.m.

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

Carsten Bock

11:40 a.m.

Hi, do you see any outgoing "INFO" Requests? Do you see anything in the logs? Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

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#id2807032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

Lee Archer

11:51 a.m.

Hi Carsten, I see the INFO requests on the target server and the packets being sent and received on the kamailio server. Logs aren't showing me anything, even in debug mode. Regards Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock Sent: 20 May 2011 09:40 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination Hi, do you see any outgoing "INFO" Requests? Do you see anything in the logs? Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

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#id28 07032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Carsten Bock

11:55 a.m.

Hi, what are the destination systems replying to the INFO-request? It should be a "200 OK" in order to reactivate the destination. If it replies something else, you need to configure the other replies: modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") See: http://www.kamailio.org/docs/modules/devel/modules_k/dispatcher.html#id2577… If it does not reply at all, the destination is not activated,,,, Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

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#id28 07032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220 _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

Lee Archer

12:06 p.m.

Hi Carsten, is this valid syntax for 3.0.4? I've been up and down the doc for the dispatcher module and can't see this in the 3.0 docs. It is replying with a 481. Thanks Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock Sent: 20 May 2011 09:55 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination Hi, what are the destination systems replying to the INFO-request? It should be a "200 OK" in order to reactivate the destination. If it replies something else, you need to configure the other replies: modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") See: http://www.kamailio.org/docs/modules/devel/modules_k/dispatcher.html#id2577… If it does not reply at all, the destination is not activated,,,, Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

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#id2 8 07032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Carsten Bock

12:18 p.m.

Hi, i think i added the feature in 3.1 to configure the valid responses. In prior versions, only the following reply codes are considered a "valid" reply: - 200 OK - 501: Cisco-Gateways reply with a "501 Not supported" to the request. - 403: Aastra-Gateways reply with a "403" to the request. - 405: Some GWs reply with a "405 Method Not Allowed" to the request. */ and it is hardcoded in the module.... So that is why your setup does not work. Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

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#id2 8 07032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock http://www.ng-voice.com mailto:carsten@ng-voice.com Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

Lee Archer

12:27 p.m.

OK, I will see what I can do at my end but it's odd that when the ping first kicks off a 481 is sent back but the server stays listed as active. Thanks for the help. Regards Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock Sent: 20 May 2011 10:18 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination Hi, i think i added the feature in 3.1 to configure the valid responses. In prior versions, only the following reply codes are considered a "valid" reply: - 200 OK - 501: Cisco-Gateways reply with a "501 Not supported" to the request. - 403: Aastra-Gateways reply with a "403" to the request. - 405: Some GWs reply with a "405 Method Not Allowed" to the request. */ and it is hardcoded in the module.... So that is why your setup does not work. Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

Hi Carsten, is this valid syntax for 3.0.4? I've been up and down the doc for the dispatcher module and can't see this in the 3.0 docs. It is replying with a 481. Thanks Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock Sent: 20 May 2011 09:55 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination Hi, what are the destination systems replying to the INFO-request? It should be a "200 OK" in order to reactivate the destination. If it replies something else, you need to configure the other replies: modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") See: http://www.kamailio.org/docs/modules/devel/modules_k/dispatcher.html#i d2577532 If it does not reply at all, the destination is not activated,,,, Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

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#id 2 8 07032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Lee Archer

2:05 p.m.

Hi all, I have it running using OPTIONS but not when using INFO. I was missing an s exten in my asterisk config. Does anyone have INFO working with Asterisk? Regards Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Lee Archer Sent: 20 May 2011 10:27 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination OK, I will see what I can do at my end but it's odd that when the ping first kicks off a 481 is sent back but the server stays listed as active. Thanks for the help. Regards Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock Sent: 20 May 2011 10:18 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination Hi, i think i added the feature in 3.1 to configure the valid responses. In prior versions, only the following reply codes are considered a "valid" reply: - 200 OK - 501: Cisco-Gateways reply with a "501 Not supported" to the request. - 403: Aastra-Gateways reply with a "403" to the request. - 405: Some GWs reply with a "405 Method Not Allowed" to the request. */ and it is hardcoded in the module.... So that is why your setup does not work. Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

...

Hi Carsten, is this valid syntax for 3.0.4? I've been up and down the doc for the dispatcher module and can't see this in the 3.0 docs. It is replying with a 481. Thanks Lee -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Carsten Bock Sent: 20 May 2011 09:55 To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] Reactivating a failed dispatcher destination Hi, what are the destination systems replying to the INFO-request? It should be a "200 OK" in order to reactivate the destination. If it replies something else, you need to configure the other replies: modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=403;code=488;class=3") See: http://www.kamailio.org/docs/modules/devel/modules_k/dispatcher.html#i d2577532 If it does not reply at all, the destination is not activated,,,, Carsten 2011/5/20 Lee Archer <Lee.Archer(a)thebigword.com>om>:

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#id 2 8 07032 Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

4939

days inactive

4940

days old

sr-users@lists.kamailio.org

Manage subscription

10 comments

3 participants

tags (0)

participants (3)

Carsten Bock
Daniel-Constantin Mierla
Lee Archer