i [3] is appended to record-route; that's useful for understanding whether subsequent requests (such as BYE) come from caller (route's from-tag==BYE's from-tag) or callee (route's from-tag==BYE's to-tag)

Default value is 1 (yes).

i [4] in the AVP, which is identified by the parameter value. It can be utilized later in the routing script.

Default value is NULL (do not insert user part into avps).

RFC3261 [5] and will set Avp value passed in Route header that were created by record_route. If ftag!=tag.from then from/to are flipped.

i [6] with it's value and removes the first URI from Route HFs.

i [7]_cookie will be inserted as serialized parameter of record-route header. Note that only user class AVPs should be passed as cookies, i.e. domain and global should be avoided.

Example 9. record_route usage

avpflags
	dialog_cookie;  # must be declared when used in script
...
setavpflag($cookie, "dialog_cookie");
setavpflag("$f./^dlg_/", "dialog_cookie");
record_route();
...

1.3.4. record_route_preset(string)

This function will put the string into Record-Route, don't use unless you know what you are doing.

Meaning of the parameters is as follows:

• string - String to be inserted into the header field.

Example 10. record_route_preset usage

...
record_route_preset("1.2.3.4:5090");
...

---