3 Jan
2004
3 Jan
'04
7:14 p.m.
On 03-01 18:59, Juha Heinanen wrote:
Greg Fausak writes:
Basically you need to record route all target refreshing requests (as
far as I know currently only INVITE and SUBSCRIBE) are target
refreshers.
Generally you don't know if a message is target refresher because some
other may be created in the future. That's the reason why it is
recommended to record-route all requests.
So it is a tradeoff between efficiency and compatibility with future
(or proprietary) extensions. If you want shorter messages
(Record-Route headers can significantly bloat SIP messages, especially
when proxy chains are involved, not even speaking of IPv6 addresses),
record route INVITE and SUBSCRIBE requests only.
If you don't care about efficiency and huge messages, record-route
everything.
Jan.
Well, that is my question. Shouldn't all
other messages
be record routed if the invite was record routed?
no, because the route recorded for initial transaction that established
the dialog will be used for all subsequent requests of that dialog. i
was just referring to your script that asked if it is an error if you
end up there. so you only need record route the initial request
(the one without to tag).