Jan Janak writes:
Wouldn't it be possible to store the timestamp of
request arrival in
an AVP at the beginning of request processing and then calculate the
difference from the current timestamp in on-send route?
that would be possible too, but it needs to be a ms timestamp, which
would not fit into an int. a ms counter that would start counting from
zero, would fit.
Also, where do you want to store the resulting delay
value, in the SIP
request itself?
no, to an avp from which i could then add it to radius accounting record
when response to invite arrives.
-- juha