This section explains the XCAP Server which allows a client to read, write, and modify application configuration data in their simservs document, a virtual XML document composed of user accessible portions of one or more HSS documents.
It uses OpenCloud’s Sh Cache Microservice to communicate with the HSS.
|For information on this piece of the Sentinel product architecture, please see XCAP Support.|
XCAP Query Examples provide several examples of XCAP queries to get and modify the simservs document.
The XCAP server tries to normalize any numbers contained in CDIV rule targets and ICB/OCB conditions before accepting the request. If any number cannot be normalized, the request is rejected. Normalization is done using the Normalization Component.
Normalization is controlled by the
NormalizationEnabled profile attribute in the
XCAPConfig profile in the
XCAPConfigProfileTable profile table.
The MMTelCDIV feature can be configured with a list of
As the name implies, any XCAP request containing a diversion rule with a target equal to a URI on this list, after they are both normalized, is rejected.
When any request is received, the XCAP server checks if the subscriber is barred from using the XCAP server (due to
Barring of Supplementary Services Management being set), or when updating diversion rules, is barred
from registering diverted numbers (
Diverted to Address Registration Barring).
To do so, it queries the Sh Cache Microservice for the
IMS-ODB-Information service indication.
If the XCAP server determines the request is not allowed, it is rejected with response code 403.