30 Nov
2014
30 Nov
'14
1:47 a.m.
lets say that invite is parallel forked to two contacts. if the call is
answered, i would like to set in reply route an accounting avp that
contains the request uri of answering branch. i have tried $T_req($ru),
but that gives the original request uri. any suggestions?
-- juha
30 Nov
30 Nov
2:44 p.m.
Juha Heinanen writes:
lets say that invite is parallel forked to two
contacts. if the call is
answered, i would like to set in reply route an accounting avp that
contains the request uri of answering branch. i have tried $T_req($ru),
but that gives the original request uri. any suggestions?
it might be possible to store in branch route request uris to an avp and
then select the correct one based on the last field of top via branch,
but that is a far too complicated solution for such a simple task as
finding out the request uri of replied request. therefore, i must be
missing something.
-- juha
1 Dec
1 Dec
3:23 a.m.
Juha Heinanen writes:
it might be possible to store in branch route request
uris to an avp and
then select the correct one based on the last field of top via branch,
but that is a far too complicated solution for such a simple task as
finding out the request uri of replied request. therefore, i must be
missing something.
another one would be to store $ru in branch route to htable using
transaction and branch index as key and then get it from there in onreply
route. still too complicated.
would it be possible to define $T(request_uri)?
-- juha
11:42 a.m.
On 01/12/14 02:23, Juha Heinanen wrote:
Juha Heinanen writes:
I think indeed that would be an option. Looks like
nobody needed this
value so far ...
it might be possible to store in branch route
request uris to an avp and
then select the correct one based on the last field of top via branch,
but that is a far too complicated solution for such a simple task as
finding out the request uri of replied request. therefore, i must be
missing something.
another one would be to store $ru in branch route to htable
using
transaction and branch index as key and then get it from there in onreply
route. still too complicated.
would it be possible to define $T(request_uri)?
I think the best way is to extend
$T_branch(...) class of pvs to have
$T_branch(ruri), or maybe even $T_branch($pv) and have $T_branch($ru)
for what you need.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
11:45 a.m.
On 01 Dec 2014, at 10:42, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:
On 01/12/14 02:23, Juha Heinanen wrote:
Do you mean the "winning" branch?
If we end up in failure route, there can be multiple branches ending up
with the same answer, like two phones sending 486. How do we handle
finding the ruri's of those?
/O
Juha Heinanen writes:
I think indeed that would be an option. Looks like
nobody needed this
value so far ...
it might be possible to store in branch route
request uris to an avp and
then select the correct one based on the last field of top via branch,
but that is a far too complicated solution for such a simple task as
finding out the request uri of replied request. therefore, i must be
missing something.
another one would be to store $ru in branch route to htable
using
transaction and branch index as key and then get it from there in onreply
route. still too complicated.
would it be possible to define $T(request_uri)?
I think the best way is to extend
$T_branch(...) class of pvs to have
$T_branch(ruri), or maybe even $T_branch($pv) and have $T_branch($ru)
for what you need.
11:55 a.m.
On 01/12/14 10:45, Olle E. Johansson wrote:
On 01 Dec 2014, at 10:42, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
For a parallel forking, indeed, there can be such
case with same code in
many branches. We have to look at tm code, I guess Jiri Kuthan or Andrei
Pelinescu implemented it long time ago (as I don't remember any work
recently on that area) and perhaps in this case it selects the first or
the last with the same code ...
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
On 01/12/14 02:23, Juha Heinanen wrote:
Do you mean the "winning" branch?
If we end up in failure route, there can be multiple branches ending up
with the same answer, like two phones sending 486. How do we handle
finding the ruri's of those? Juha Heinanen writes:
I think indeed that would be an option. Looks like
nobody needed this
value so far ...
it might be possible to store in branch route
request uris to an avp and
then select the correct one based on the last field of top via branch,
but that is a far too complicated solution for such a simple task as
finding out the request uri of replied request. therefore, i must be
missing something.
another one would be to store $ru in branch route to htable
using
transaction and branch index as key and then get it from there in onreply
route. still too complicated. would it be possible to define $T(request_uri)?
I think the best way is to extend $T_branch(...) class of pvs to have
$T_branch(ruri), or maybe even $T_branch($pv) and have $T_branch($ru)
for what you need.
12:04 p.m.
Daniel-Constantin Mierla writes:
I think the best way is to extend $T_branch(...) class
of pvs to have
$T_branch(ruri), or maybe even $T_branch($pv) and have $T_branch($ru)
for what you need.
$T_branch(ruri) or $T(ruri) would be fine to me.
it is very strange that no-one has so far been interested in where
calls get routed to.
-- juha
12:10 p.m.
On 01/12/14 11:04, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I most of the case I need the source ip and port of the reply, all
related to the r-uri is handled in branch_route.
And indeed, give that you are one of the first people using SER, it took
a long time for someone to need this attribute while processing the reply...
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
I think the best way is to extend $T_branch(...)
class of pvs to have
$T_branch(ruri), or maybe even $T_branch($pv) and have $T_branch($ru)
for what you need.
$T_branch(ruri) or $T(ruri) would be fine to me.
it is very strange that no-one has so far been interested in where
calls get routed to.
12:22 p.m.
Daniel-Constantin Mierla writes:
I most of the case I need the source ip and port of
the reply, all
related to the r-uri is handled in branch_route.
how can you set translated request uri accounting attribute in branch
route when the call is parallel forked? ip and port of the reply do not
tell which aor the call went.
And indeed, give that you are one of the first people
using SER, it took
a long time for someone to need this attribute while processing the reply...
i had a bug in my config. it didn't set translated request uri
accounting attribute correctly when call is parallel forked. when i
started to investigate, it turned out that there was no easy way to fix
the bug.
-- juha
12:27 p.m.
On 01/12/14 11:22, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Accounting module takes the r-uri from winning branch, afaik -- if you
account $ru via acc *_extra parameter.
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
I most of the case I need the source ip and port
of the reply, all
related to the r-uri is handled in branch_route.
how can you set translated
request uri accounting attribute in branch
route when the call is parallel forked? ip and port of the reply do not
tell which aor the call went.
And indeed, give that you are one of the first
people using SER, it took
a long time for someone to need this attribute while processing the reply...
i had
a bug in my config. it didn't set translated request uri
accounting attribute correctly when call is parallel forked. when i
started to investigate, it turned out that there was no easy way to fix
the bug.
2 Dec
2 Dec
10:42 a.m.
On 01/12/14 11:37, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I just committed a patch to master to get the r-uri in config when
handling a reply via tm onreply_route block:
-
https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables?&#t_branc…
Should be useful when one needs the value in config file.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Accounting module takes the r-uri from winning
branch, afaik -- if you
account $ru via acc *_extra parameter.
you are correct. i tested and that indeed
is the case.
3645
days inactive
3648
days old
11 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Juha Heinanen -
Olle E. Johansson