Explicit Feature Preference
RFC3841 defines the two headers that a UA can use to explicitly specify the features the target UA must support, including:
Accept-Contact:
— UEs the session initiator would like to reach
Reject-Contact:
— UEs the session initiator does not want to reach
When the Oracle Communications Core Session Manager receives messages that includes these headers, it gathers all the contacts associated with the AOR and creates a target list using preferential routing calculations. The example below, drawn from RFC 3841, specifies the desire to route to a mobile device that can accept the INVITE method.
Accept-Contact: *;mobility="mobile";methods="INVITE"