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

[OpenSIPS-Users] ERROR:tm:t_forward_nonack: no branch for forwarding

2010-10-18 Thread Najib Hara 

Hi everybody,

I don't know if this problem is already solved but I can't find any related 
information. I'm trying to relay requests through OpenSIPS to another OpenSIPS 
server together on the same machine. And I got this each time:



Oct 18
11:53:00 Opensips opensips1[17997]: ERROR:tm:t_forward_nonack: no branch
for forwarding

Oct 18
11:53:00 Opensips opensips1[17997]: ERROR:tm:w_t_relay: t_forward_nonack
failed..
Oct 18 11:53:00 Opensips opensips1[17997]:
CRITICAL:tm:t_should_relay_response: pick_branch failed (lowest==-1) for code
488
My t_relay function is used on the request route.Anyone could help me with this 
?
Thanks in advance


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

[OpenSIPS-Users] 503 Server address has exceeded max calls in flight 75

2010-10-18 Thread thrillerbee 
Occasionally, I'm receiving a '503 Server address has exceed max calls in
flight 75' from the b2bua opensips instance.  What does this indicate?  How
is it prevented?

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

Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not Working (Bug?)

2010-10-18 Thread Brett Woollum 
Hi Anca, 

I set debug=6 but it does not appear to print any more detailed information to 
my log (/var/log/messages). 

I reviewed the sip trace I posted at 
http://www.woollum.com/temp/opensips_trace.html and I still cannot find any 
packets that are missing the header. The error log I posted at 
http://www.woollum.com/temp/opensips.txt says that the To field, From field, 
and RR field could not be parsed. It seems as though the B2BUA module tried to 
open a new leg but didn't send the information along? Does that make sense? 
From the log earlier: 
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [] in status 5:  .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:b2b_entities:b2b_prescript_f: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [] in status 5:  .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE STARTING INVITE 
null sip:sa...@1.2.3.4
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [] in status 5:  .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:rr:record_route: 
From parsing failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [] in status 5:  .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:new_t: no valid 
From in INVITE
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:tm:t_newtran: new_t 
failed
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ERROR:core:parse_to: 
unexpected char [] in status 5:  .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: ERROR:core:parse_to: 
unexpected char [] in status 5:  .
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: 
ERROR:core:parse_from_header: bad from header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: 
ERROR:core:pv_get_from_attr: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5172]: 
ERROR:b2b_entities:b2b_tm_cback: cannot parse From header
Oct 12 19:34:16 sip01 /usr/local/sbin/opensips[5167]: ROUTE 8 ENDING INVITE 
null sip:sa...@10.20.1.225:5062
Oct 12 19:34:17 sip01 /usr/local/sbin/opensips[5168]: 
ERROR:b2b_entities:b2b_prescript_f: No dialog found, callid= [B2B.50.3250981], 
method=REFER Brett Woollum 

br...@woollum.com 


- Original Message - 
From: Anca Vamanu a...@opensips.org 
To: users@lists.opensips.org 
Sent: Thursday, October 14, 2010 12:45:19 AM GMT -08:00 US/Canada Pacific 
Subject: Re: [OpenSIPS-Users] B2BUA Transfers Intermittently Working/Not 
Working (Bug?) 

Hi Brett, 

You need to run a network trace and catch the message for which you get this 
error: 

ERROR:core:parse_to: unexpected char [] in status 5:  

You can run opensips in debug mode ( set 'debug=6' ) to see info from the 
message and be able to find it in the network trace. 

From the logs it seems that a message ( possibly REFER ) has a bad From header 
and OpenSIPS is not able to process right. 

Regards, 
-- 
Anca Vamanu www.voice-system.ro 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users