List Info

Thread: load_contacts() forgets bflag of "location" table




load_contacts() forgets bflag of "location" table
country flaguser name
United States
2007-10-23 13:30:08
Bugs item #1818610, was opened at 2007-10-23 08:06
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourcefo
rge.net/tracker/?func=detail&atid=743020&aid=1818610
&group_id=139143

Please note that this message will contain a full copy of
the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: ver 1.2.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Iñaki Baz (ibc_sf)
Assigned to: Nobody/Anonymous (nobody)
Summary: [lcr] load_contacts() forgets bflag of
"location" table

Initial Comment:
In serial forwarding with different "q" values
contacts bflags are forgotten.

I have this "location" table:

  username    domain       contact                    
received               cflags   q
  800         domain.org   sip:800192.168.1.33:5060  
sip:82.35.221.20:5060  192      0.80
  800         domain.org   sip:800192.168.1.33:5080  
sip:82.35.221.20:5080  192      0.50

Both contacts behind NAT and different "q".

I fix NAT for each branch in "branch_route[1]" in
case of parallel forking. It works OK.


But since I added serial forwarding with load_contacts() and
next_contacts() after lookup("location") and
next_contacts() in "failure_route[1]" NAT doesn't
work because those two functions forget the bflag(6).

In fact, the issue is worse since in
"failure_route[1]" I do next_contacts() but in
this case the INVITE is sent to 192.168.1.133:5080 instead
the public IP !!!!

Is there any way to solve it? or is it a bug on lcr
functions handling contacts bflags and "received"
field?


------------------------------------------------------------
----------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-10-23 11:30

Message:
Logged In: NO 

i think this

http://openser.svn.sourceforge.net/v
iewvc/openser?view=rev&revision=2696

fixes your problem.

because of the complexity, there will not be a backport to
1.2.

-- juha

------------------------------------------------------------
----------

Comment By: Iñaki Baz (ibc_sf)
Date: 2007-10-23 11:04

Message:
Logged In: YES 
user_id=1844020
Originator: YES

Sorry, I forgot.
It's OpenSer 1.2.2-1 of Debian Sid.

------------------------------------------------------------
----------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-10-23 09:40

Message:
Logged In: NO 

when you file an item like this, please tell which version
of openser this
applies to.

-- juha


------------------------------------------------------------
----------

You can respond by visiting: 
https://sourcefo
rge.net/tracker/?func=detail&atid=743020&aid=1818610
&group_id=139143

_______________________________________________
Devel mailing list
Developenser.org
htt
p://openser.org/cgi-bin/mailman/listinfo/devel

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )