8 Aug
2012
8 Aug
'12
1:53 p.m.
Hi, AFAIK kamailio does not add Path header for a REGISTER that is routed
to another server. Adding it should be straightforward:
There is no need for a new script function. Instead use the existing
loose_route() function, but:
If the request method is REGISTER then add Path header(s) instead of
Record-Route header(s), which the exact SAME value (this includes Outbound
flow token and ;ob param, when implemented). No more.
Cheers.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
8 Aug
8 Aug
1:55 p.m.
2012/8/8 Iñaki Baz Castillo <ibc(a)aliax.net>
Hi, AFAIK kamailio does not add Path header for a REGISTER that is routed to another
server. Adding it should be straightforward:
There is no need for a new script function. Instead use the existing loose_route()
function, but:
If the request method is REGISTER then add Path header(s) instead of Record-Route
header(s), which the exact SAME value (this includes Outbound flow token and ;ob param,
when implemented). No more.
Ok, there is already support for this via:
http://kamailio.org/docs/modules/3.3.x/modules_k/path.html#id2537563
I didn't realize of it. I expect that add_path() is just a wrapper on
top of loose_route() by replacing "Record-Route" with "Path".
Cheers.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
2:05 p.m.
On 08.08.2012 12:55, Iñaki Baz Castillo wrote:
2012/8/8 Iñaki Baz Castillo <ibc(a)aliax.net>
Not exactly. I takes care of choosing the proper IP address (outgoing
interface) but does not add double-headers like RR does. Further, the
add_path_received() function is useful for far-end NAT traversal.
regards
Klaus
Hi, AFAIK kamailio does not add Path header for a REGISTER that is routed to another
server. Adding it should be straightforward:
There is no need for a new script function. Instead use the existing loose_route()
function, but:
If the request method is REGISTER then add Path header(s) instead of Record-Route
header(s), which the exact SAME value (this includes Outbound flow token and ;ob param,
when implemented). No more.
Ok, there is already support for this via:
http://kamailio.org/docs/modules/3.3.x/modules_k/path.html#id2537563
I didn't realize of it. I expect that add_path() is just a wrapper on
top of loose_route() by replacing "Record-Route" with "Path".
2:09 p.m.
2012/8/8 Klaus Darilion <klaus.mailinglists(a)pernau.at>at>:
Not exactly. I takes care of choosing the proper IP
address (outgoing
interface) but does not add double-headers like RR does.
I don't understand why. If we require double RR (in same cases as when
there is transport bridging) then we also need double Path in the same
cases. The registrar will send us (to kamailio) an initial request
with Route header(s) mirroring the Path header(s) we added to the
REGISTER, so we need double Path in the same cases in which we need
double RR. Am I wrong?
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
10 Aug
10 Aug
1:50 p.m.
On 08.08.2012 13:09, Iñaki Baz Castillo wrote:
2012/8/8 Klaus Darilion
<klaus.mailinglists(a)pernau.at>at>:
I think so. Double RR is needed when multihoming is used:
client<---------ext-kamailio-int--------->registrar
The client needs to see "ext" as next hop whereas the registrar needs to
see "int" as next hop during in-dialog requests
The "path" is only used by the registrar (as pre-loaded route set on
out-of-dialog requests). Thus, as only the registrar uses the learned
path, only the "int" IP address needs to be added to path.
regards
Klaus
Not exactly. I takes care of choosing the proper
IP address (outgoing
interface) but does not add double-headers like RR does.
I don't understand why. If we require double RR (in same cases as when
there is transport bridging) then we also need double Path in the same
cases. The registrar will send us (to kamailio) an initial request
with Route header(s) mirroring the Path header(s) we added to the
REGISTER, so we need double Path in the same cases in which we need
double RR. Am I wrong?
4487
days inactive
4489
days old
4 comments
2 participants
participants (2)
-
Iñaki Baz Castillo -
Klaus Darilion