subject:"Re\: \[OpenSIPS\-Users\] Dispatcher failover \& re\-enabling with probing"

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

2010-10-22 Thread Bogdan-Andrei Iancu

Hi,

what group are you using for your destination (in dispatcher) ? if 0, 
use another one :D...there is an issue there...

Regards,
Bogdan

thrillerbee wrote:
 I could still use some help on understanding what I'm missing that is 
 preventing gws from transitioning back into the 'active' state from 
 'probing'.  Currently, I have to babysit this OpenSIPS instance.

 Again, to summarize, when dispatcher detects a failure, it puts the gw 
 into 'probing' state  begins sending OPTIONS messages to the failed 
 gw.  Even though the gateway begins replying with 200s, dispatcher 
 never returns it to an 'active' state.  I have to restart OpenSIPS to 
 return it to an 'active' state.

 Here are the relevant pieces of my config script:
 # - dispatcher params -
 modparam(dispatcher, flags, 2)
 modparam(dispatcher, dst_avp, $avp(i:271))
 modparam(dispatcher, attrs_avp, $avp(i:272))
 modparam(dispatcher, grp_avp, $avp(i:273))
 modparam(dispatcher, cnt_avp, $avp(i:274))
 modparam(dispatcher, ds_ping_interval, 1)
 modparam(dispatcher, ds_probing_threshhold, 32)
 modparam(dispatcher, ds_probing_mode, 0)
 modparam(dispatcher, options_reply_codes, 501, 403, 200)

 failure_route[1]
 {
 if (t_was_cancelled()) {
 exit;
 }
 if ((t_check_status(408))  (t_local_replied(last)))
 {
 xlog(L_ERR,Gateway Failure! $ci\n);
 ds_mark_dst(p);
 t_on_failure(1);
 t_relay();
 }
 }

 Again, any assistance would be greatly appreciated.

 Thanks.



 On Mon, Oct 18, 2010 at 7:31 AM, thrillerbee thriller...@gmail.com 
 mailto:thriller...@gmail.com wrote:

 Anca,

 I have configured the ds_probing_threshold parameter which allows
 me to adjust when I gw goes from active to probing.

 However, my issue is getting the gw back to active.  For some
 reason, it will never transition back - even with successful 200
 OK responses to the OPTIONS messages that are triggered when a gw
 goes to probing.  The examples below show that I can't even
 force it back to active from probing to active with MI commands -
 I have to restart OpenSIPS.

 Thanks.


 On Mon, Oct 18, 2010 at 5:50 AM, Anca Vamanu a...@opensips.org
 mailto:a...@opensips.org wrote:

 Hi Thrillerbee,

 You can try to adjust the time when a gateway  state is
 changed into probing by setting the ds_probing_threshhold ||
 parameter
 
 (http://www.opensips.org/html/docs/modules/devel/dispatcher.html#id250525).

 Regards,
 -- 

 Anca Vamanu
 www.voice-system.ro http://www.voice-system.ro


 On 10/16/2010 08:01 AM, thrillerbee wrote:
 I have been able to get the dispatcher module to detect a gw
 failure and put it into a probing state  route traffic
 elsewhere.  However, when the gw returns ( begins responding
 to OPTIONS with 200s), dispatcher never puts it back in the
 active state.

 In fact, I cannot even manually put the server back in the
 active state with mi functions.  I can put it in an inactive
 state, but it returns to probing if I try to set it to active:

 ogw1:~# opensipsctl fifo ds_list
 SET_NO:: 1
 SET:: 0
 URI:: sip:12.121.80.38 flag=P
 URI:: sip:12.121.80.39 flag=A
 URI:: sip:12.121.80.40 flag=A
 ogw1:~# opensipsctl fifo ds_set_state i 0 sip:12.121.80.38 
 ogw1:~# opensipsctl fifo ds_list
 SET_NO:: 1
 SET:: 0
 URI:: sip:12.121.80.38 flag=I
 URI:: sip:12.121.80.39 flag=A
 URI:: sip:12.121.80.40 flag=A
 ogw1:~# opensipsctl fifo ds_set_state a 0 sip:12.121.80.38 
 ogw1:~# opensipsctl fifo ds_list
 SET_NO:: 1
 SET:: 0
 URI:: sip:12.121.80.38 flag=P
 URI:: sip:12.121.80.39 flag=A
 URI:: sip:12.121.80.40 flag=A

 Is there some setting that I am missing that allows gateways
 to transition from probing to active?

 Thanks.


 ___
 Users mailing list
 Users@lists.opensips.org mailto:Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users

 ___
 Users mailing list
 Users@lists.opensips.org mailto:Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users



 

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


-- 
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
15 - 19 November 2010, Edison, New Jersey, USA
www.voice-system.ro

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

2010-10-22 Thread thrillerbee

Thank you!
I'll give that a shot  report back.

Ryan

On Fri, Oct 22, 2010 at 12:07 PM, Bogdan-Andrei Iancu 
bog...@voice-system.ro wrote:

 Hi,

 what group are you using for your destination (in dispatcher) ? if 0,
 use another one :D...there is an issue there...

 Regards,
 Bogdan

 thrillerbee wrote:
  I could still use some help on understanding what I'm missing that is
  preventing gws from transitioning back into the 'active' state from
  'probing'.  Currently, I have to babysit this OpenSIPS instance.
 
  Again, to summarize, when dispatcher detects a failure, it puts the gw
  into 'probing' state  begins sending OPTIONS messages to the failed
  gw.  Even though the gateway begins replying with 200s, dispatcher
  never returns it to an 'active' state.  I have to restart OpenSIPS to
  return it to an 'active' state.
 
  Here are the relevant pieces of my config script:
  # - dispatcher params -
  modparam(dispatcher, flags, 2)
  modparam(dispatcher, dst_avp, $avp(i:271))
  modparam(dispatcher, attrs_avp, $avp(i:272))
  modparam(dispatcher, grp_avp, $avp(i:273))
  modparam(dispatcher, cnt_avp, $avp(i:274))
  modparam(dispatcher, ds_ping_interval, 1)
  modparam(dispatcher, ds_probing_threshhold, 32)
  modparam(dispatcher, ds_probing_mode, 0)
  modparam(dispatcher, options_reply_codes, 501, 403, 200)
 
  failure_route[1]
  {
  if (t_was_cancelled()) {
  exit;
  }
  if ((t_check_status(408))  (t_local_replied(last)))
  {
  xlog(L_ERR,Gateway Failure! $ci\n);
  ds_mark_dst(p);
  t_on_failure(1);
  t_relay();
  }
  }
 
  Again, any assistance would be greatly appreciated.
 
  Thanks.
 
 
 
  On Mon, Oct 18, 2010 at 7:31 AM, thrillerbee thriller...@gmail.com
  mailto:thriller...@gmail.com wrote:
 
  Anca,
 
  I have configured the ds_probing_threshold parameter which allows
  me to adjust when I gw goes from active to probing.
 
  However, my issue is getting the gw back to active.  For some
  reason, it will never transition back - even with successful 200
  OK responses to the OPTIONS messages that are triggered when a gw
  goes to probing.  The examples below show that I can't even
  force it back to active from probing to active with MI commands -
  I have to restart OpenSIPS.
 
  Thanks.
 
 
  On Mon, Oct 18, 2010 at 5:50 AM, Anca Vamanu a...@opensips.org
  mailto:a...@opensips.org wrote:
 
  Hi Thrillerbee,
 
  You can try to adjust the time when a gateway  state is
  changed into probing by setting the ds_probing_threshhold ||
  parameter
  (
 http://www.opensips.org/html/docs/modules/devel/dispatcher.html#id250525).
 
  Regards,
  --
 
  Anca Vamanu
  www.voice-system.ro http://www.voice-system.ro
 
 
  On 10/16/2010 08:01 AM, thrillerbee wrote:
  I have been able to get the dispatcher module to detect a gw
  failure and put it into a probing state  route traffic
  elsewhere.  However, when the gw returns ( begins responding
  to OPTIONS with 200s), dispatcher never puts it back in the
  active state.
 
  In fact, I cannot even manually put the server back in the
  active state with mi functions.  I can put it in an inactive
  state, but it returns to probing if I try to set it to active:
 
  ogw1:~# opensipsctl fifo ds_list
  SET_NO:: 1
  SET:: 0
  URI:: sip:12.121.80.38 flag=P
  URI:: sip:12.121.80.39 flag=A
  URI:: sip:12.121.80.40 flag=A
  ogw1:~# opensipsctl fifo ds_set_state i 0 sip:12.121.80.38
  ogw1:~# opensipsctl fifo ds_list
  SET_NO:: 1
  SET:: 0
  URI:: sip:12.121.80.38 flag=I
  URI:: sip:12.121.80.39 flag=A
  URI:: sip:12.121.80.40 flag=A
  ogw1:~# opensipsctl fifo ds_set_state a 0 sip:12.121.80.38
  ogw1:~# opensipsctl fifo ds_list
  SET_NO:: 1
  SET:: 0
  URI:: sip:12.121.80.38 flag=P
  URI:: sip:12.121.80.39 flag=A
  URI:: sip:12.121.80.40 flag=A
 
  Is there some setting that I am missing that allows gateways
  to transition from probing to active?
 
  Thanks.
 
 
  ___
  Users mailing list
  Users@lists.opensips.org mailto:Users@lists.opensips.org
  http://lists.opensips.org/cgi-bin/mailman/listinfo/users
 
  ___
  Users mailing list
  Users@lists.opensips.org mailto:Users@lists.opensips.org
  http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

2010-10-22 Thread thrillerbee

Bogan,

That resolved it.  Thanks for the advice.

Ryan

On Fri, Oct 22, 2010 at 12:32 PM, thrillerbee thriller...@gmail.com wrote:

 Thank you!
 I'll give that a shot  report back.

 Ryan


 On Fri, Oct 22, 2010 at 12:07 PM, Bogdan-Andrei Iancu 
 bog...@voice-system.ro wrote:

 Hi,

 what group are you using for your destination (in dispatcher) ? if 0,
 use another one :D...there is an issue there...

 Regards,
 Bogdan

 thrillerbee wrote:
  I could still use some help on understanding what I'm missing that is
  preventing gws from transitioning back into the 'active' state from
  'probing'.  Currently, I have to babysit this OpenSIPS instance.
 
  Again, to summarize, when dispatcher detects a failure, it puts the gw
  into 'probing' state  begins sending OPTIONS messages to the failed
  gw.  Even though the gateway begins replying with 200s, dispatcher
  never returns it to an 'active' state.  I have to restart OpenSIPS to
  return it to an 'active' state.
 
  Here are the relevant pieces of my config script:
  # - dispatcher params -
  modparam(dispatcher, flags, 2)
  modparam(dispatcher, dst_avp, $avp(i:271))
  modparam(dispatcher, attrs_avp, $avp(i:272))
  modparam(dispatcher, grp_avp, $avp(i:273))
  modparam(dispatcher, cnt_avp, $avp(i:274))
  modparam(dispatcher, ds_ping_interval, 1)
  modparam(dispatcher, ds_probing_threshhold, 32)
  modparam(dispatcher, ds_probing_mode, 0)
  modparam(dispatcher, options_reply_codes, 501, 403, 200)
 
  failure_route[1]
  {
  if (t_was_cancelled()) {
  exit;
  }
  if ((t_check_status(408))  (t_local_replied(last)))
  {
  xlog(L_ERR,Gateway Failure! $ci\n);
  ds_mark_dst(p);
  t_on_failure(1);
  t_relay();
  }
  }
 
  Again, any assistance would be greatly appreciated.
 
  Thanks.
 
 
 
  On Mon, Oct 18, 2010 at 7:31 AM, thrillerbee thriller...@gmail.com
  mailto:thriller...@gmail.com wrote:
 
  Anca,
 
  I have configured the ds_probing_threshold parameter which allows
  me to adjust when I gw goes from active to probing.
 
  However, my issue is getting the gw back to active.  For some
  reason, it will never transition back - even with successful 200
  OK responses to the OPTIONS messages that are triggered when a gw
  goes to probing.  The examples below show that I can't even
  force it back to active from probing to active with MI commands -
  I have to restart OpenSIPS.
 
  Thanks.
 
 
  On Mon, Oct 18, 2010 at 5:50 AM, Anca Vamanu a...@opensips.org
  mailto:a...@opensips.org wrote:
 
  Hi Thrillerbee,
 
  You can try to adjust the time when a gateway  state is
  changed into probing by setting the ds_probing_threshhold ||
  parameter
  (
 http://www.opensips.org/html/docs/modules/devel/dispatcher.html#id250525
 ).
 
  Regards,
  --
 
  Anca Vamanu
  www.voice-system.ro http://www.voice-system.ro
 
 
  On 10/16/2010 08:01 AM, thrillerbee wrote:
  I have been able to get the dispatcher module to detect a gw
  failure and put it into a probing state  route traffic
  elsewhere.  However, when the gw returns ( begins responding
  to OPTIONS with 200s), dispatcher never puts it back in the
  active state.
 
  In fact, I cannot even manually put the server back in the
  active state with mi functions.  I can put it in an inactive
  state, but it returns to probing if I try to set it to active:
 
  ogw1:~# opensipsctl fifo ds_list
  SET_NO:: 1
  SET:: 0
  URI:: sip:12.121.80.38 flag=P
  URI:: sip:12.121.80.39 flag=A
  URI:: sip:12.121.80.40 flag=A
  ogw1:~# opensipsctl fifo ds_set_state i 0 sip:12.121.80.38
  ogw1:~# opensipsctl fifo ds_list
  SET_NO:: 1
  SET:: 0
  URI:: sip:12.121.80.38 flag=I
  URI:: sip:12.121.80.39 flag=A
  URI:: sip:12.121.80.40 flag=A
  ogw1:~# opensipsctl fifo ds_set_state a 0 sip:12.121.80.38
  ogw1:~# opensipsctl fifo ds_list
  SET_NO:: 1
  SET:: 0
  URI:: sip:12.121.80.38 flag=P
  URI:: sip:12.121.80.39 flag=A
  URI:: sip:12.121.80.40 flag=A
 
  Is there some setting that I am missing that allows gateways
  to transition from probing to active?
 
  Thanks.
 
 
  ___
  Users mailing list
  Users@lists.opensips.org mailto:Users@lists.opensips.org
  http://lists.opensips.org/cgi-bin/mailman/listinfo/users
 
  ___
  Users mailing list
  Users@lists.opensips.org mailto:Users@lists.opensips.org

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

2010-10-18 Thread Anca Vamanu


Hi Thrillerbee,

You can try to adjust the time when a gateway  state is changed into 
probing by setting the ds_probing_threshhold || parameter 
(http://www.opensips.org/html/docs/modules/devel/dispatcher.html#id250525).


Regards,
--

Anca Vamanu
www.voice-system.ro


On 10/16/2010 08:01 AM, thrillerbee wrote:
I have been able to get the dispatcher module to detect a gw failure 
and put it into a probing state  route traffic elsewhere.  However, 
when the gw returns ( begins responding to OPTIONS with 200s), 
dispatcher never puts it back in the active state.


In fact, I cannot even manually put the server back in the active 
state with mi functions.  I can put it in an inactive state, but it 
returns to probing if I try to set it to active:


ogw1:~# opensipsctl fifo ds_list
SET_NO:: 1
SET:: 0
URI:: sip:12.121.80.38 flag=P
URI:: sip:12.121.80.39 flag=A
URI:: sip:12.121.80.40 flag=A
ogw1:~# opensipsctl fifo ds_set_state i 0 sip:12.121.80.38
ogw1:~# opensipsctl fifo ds_list
SET_NO:: 1
SET:: 0
URI:: sip:12.121.80.38 flag=I
URI:: sip:12.121.80.39 flag=A
URI:: sip:12.121.80.40 flag=A
ogw1:~# opensipsctl fifo ds_set_state a 0 sip:12.121.80.38
ogw1:~# opensipsctl fifo ds_list
SET_NO:: 1
SET:: 0
URI:: sip:12.121.80.38 flag=P
URI:: sip:12.121.80.39 flag=A
URI:: sip:12.121.80.40 flag=A

Is there some setting that I am missing that allows gateways to 
transition from probing to active?


Thanks.


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

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

Re: [OpenSIPS-Users] Dispatcher failover re-enabling with probing

4 matches

Site Navigation

Mail list logo

Footer information