26 Jul
2007
26 Jul
'07
5 p.m.
I was looking at the openser config generated using the online
sipwise wizard. They implement conditional call forwarding using:
if($avp(s:cfc) != NULL)
{
avp_pushto("$ru", "$avp(s:cfc)");
setflag(29);
append_branch();
t_on_branch("1");
xlog("L_INFO", "CFC detected - M=$rm RURI=$ru F=$fu
T=$tu IP=$si ID=$ci\n");
route(13);
}
branch_route[1]
{
if(is_domain_local("$rd"))
{
xlog("L_INFO", "Dropping local branch - M=$rm RURI=
$ru F=$fu T=$tu IP=$si ID=$ci\n");
drop();
}
}
Suppose an invite gets to this point and ruri is changed to another
local user. does this drop() in branch_route prevents that invite to
be relayed? does it still go through route(13) ?
I'm still a newbie trying to better understand the working of openser
functions. I'll greatly appreciate if someone can briefly describe
when it makes sense to use "append_branch()"
Thanks in advance for your help.
--
Zahid
26 Jul
26 Jul
7:37 p.m.
Hi,
The config is designed to never relay a request to itself, but instead
do recursive route processing. So if you do a CFC to a local user, the
config will take care to do a lookup before a relay, which will change
the request uri to the IP of the CF target.
Andreas
Zahid Mehmood wrote:
I was looking at the openser config generated using
the online sipwise
wizard. They implement conditional call forwarding using:
if($avp(s:cfc) != NULL)
{
avp_pushto("$ru", "$avp(s:cfc)");
setflag(29);
append_branch();
t_on_branch("1");
xlog("L_INFO", "CFC detected - M=$rm RURI=$ru F=$fu
T=$tu IP=$si ID=$ci\n");
route(13);
}
branch_route[1]
{
if(is_domain_local("$rd"))
{
xlog("L_INFO", "Dropping local branch - M=$rm RURI=$ru
F=$fu T=$tu IP=$si ID=$ci\n");
drop();
}
}
Suppose an invite gets to this point and ruri is changed to another
local user. does this drop() in branch_route prevents that invite to be
relayed? does it still go through route(13) ?
I'm still a newbie trying to better understand the working of openser
functions. I'll greatly appreciate if someone can briefly describe
when it makes sense to use "append_branch()"
Thanks in advance for your help.
8:09 p.m.
Andreas,
Thanks for your reply. I understand that part. Is that a
best-practice to not relay a packet to yourself? I was trying to
implement serial forking based on the example for voice-systems and I'm
running into some issues when doing a simple t_relay() and that is when
I started looking for a better way to do this.
I'm still not clear about the use of t_on_branch. In this case, when
is it really called?
--
Zahid
-----Original Message-----
From: Andreas Granig [mailto:agranig@sipwise.com]
Sent: Thursday, July 26, 2007 1:37 PM
To: Zahid Mehmood
Cc: users(a)openser.org
Subject: Re: [OpenSER-Users] t_on_branch -- using drop() question?
Hi,
The config is designed to never relay a request to itself, but instead
do recursive route processing. So if you do a CFC to a local user, the
config will take care to do a lookup before a relay, which will change
the request uri to the IP of the CF target.
Andreas
Zahid Mehmood wrote:
I was looking at the openser config generated using
the online sipwise
wizard. They implement conditional call forwarding
using:
if($avp(s:cfc) != NULL)
{
avp_pushto("$ru", "$avp(s:cfc)");
setflag(29);
append_branch();
t_on_branch("1");
xlog("L_INFO", "CFC detected - M=$rm RURI=$ru F=$fu
T=$tu IP=$si ID=$ci\n");
route(13);
}
branch_route[1]
{
if(is_domain_local("$rd"))
{
xlog("L_INFO", "Dropping local branch - M=$rm RURI=$ru
F=$fu T=$tu IP=$si ID=$ci\n");
drop();
}
}
Suppose an invite gets to this point and ruri is changed to another
local user. does this drop() in branch_route prevents that invite to
be
relayed? does it still go through route(13) ?
I'm still a newbie trying to better understand the working of openser
functions. I'll greatly appreciate if someone can briefly describe
when it makes sense to use "append_branch()"
Thanks in advance for your help.
8:16 p.m.
Hi,
There was a discussion about relaying to yourself vs. recursive loops
through routes:
http://openser.org/pipermail/users/2007-July/012042.html
In the sipwise config, heavy sip-uri manipulation is done after
appending a branch (which is necessary after failure-route), so I append
a branch, manipulate the r-uri, append another branch with the final
r-uri and on relay drop the unneeded one.
I guess we'll discuss some best-practices in Rome in September to
optimize it a bit, right, Bogdan? ;o)
Andreas
Zahid Mehmood wrote:
Andreas,
Thanks for your reply. I understand that part. Is that a
best-practice to not relay a packet to yourself? I was trying to
implement serial forking based on the example for voice-systems and I'm
running into some issues when doing a simple t_relay() and that is when
I started looking for a better way to do this.
I'm still not clear about the use of t_on_branch. In this case, when
is it really called?
6128
days inactive
6128
days old
3 comments
2 participants
participants (2)
-
Andreas Granig -
Zahid Mehmood