ILS/GDPR

• As the GDPR feature is limited to a single GDPR partitioning scheme per cluster, multi-tenancy is not achievable. Therefore GDPR is only supported for dedicated customer deployments. Shared Architecture deployments using GDPR are unsupported. Such dial plan designs are recommended to use static routing mechanisms.
• GDPR Failover scenarios have not been investigated. These open a series of questions pertaining to:
  • Overlapping AAR requirements in hybrid breakout (LBO/CBO) scenarios. This is a corner case.
  • Lack of FAC support for GDPR PSTN Failover (this is a generic caveat for CUCM redirected call flows). This feature gap’s limitations are detailed in CSCuv41940 (sev6). PSTN Failover is not a present requirement, making FAC support thereof a corner case only.
• +E.164 model provisioning (plus-prefixed patterns e.g. +1408123XXXX) for GDPR Advertised and Blocked Patterns fail - fix targeted for 11.5.1ES1
• There are several AXL limitations for ILS and GDPR configurations that singletons. These do not support ‘list’ methods, and as such cannot currently be bulk loaded. At present, ILS Configuration and GDPR Learned Partitions will require static configuration on CUCM.