Routing Based on UA Capabilities

In compliance with RFC 3841, the Oracle Communications Core Session Manager is able to make forwarding and forking decisions based on preferences indicated by the UA. To do this, the Oracle Communications Core Session Manager evaluates each callee’s AOR contact to determine the capabilities advertised by the UA and uses this information to make forwarding and forking decisions.

Prior to this support, the Oracle Communications Core Session Manager made routing preference decisions solely via the q value present in the contact header. In cases where the preferences were equal, the Oracle Communications Core Session Manager simply forwarded to those contacts simultaneously (parallel forking). In cases where the q value were not equal, the Oracle Communications Core Session Manager forwarded in sequence (sequential forking), forwarding to the highest q value first.

The Oracle Communications Core Session Manager now extends upon this functionality by scoring contacts, based on their capabilities, and making forwarding decisions using that score in addition to the q value.

There is no additional Oracle Communications Core Session Manager configuration required to enable or invoke this processing. This functionality is supported for HSS, ENUM and Local Database configurations.