Record-Route Clause Samples
Record-Route. When the INVITE is crossing a trust domain then it is up to the sending party (S-CSC or SB/SCIM) to determine (based on configuration parameters) whether to Record-Route or not. If the INVITE request is to be Record-Routed then the sending entity shall include a Record-Route header containing its own SIP URI.
Record-Route. If the Media Server intends to act in monitored mode for a session and is implemented as a proxy then it MUST include a Record-Route header in order to ensure it receives any subsequent requests for the dialog.
Record-Route. Support for the Record-Route header is mandatory for both UACs and UASs. The Record-Route header is inserted to INVITE request by a Proxy to ensure that it will receive all subsequence requests and responses belong to the same session. Reference is made to section 16.12 of RFC 3261 for example flows on the use of this header.