IMPORTANT

Running the DM/PM rules is CPU- and memory-intensive because each rule is issued for every sub-rule linearly. If you do not use DM/PM rules sparingly, it becomes difficult to manage the number of DM/PM rules or sub-rules applied to a call. Ribbon recommends issuing no more than 80-100 sub-rules per call.

The ad Attribute Map Profile is added to the CLI. This profile allows the user to configure flexible AD attributes. For each attribute there is an AD attribute identified. This AD attribute identified is used as referenced in all other entities.

Command Syntax

The following command is used to create the AD Attribute Map Profile.

adAttributeMapProfile Command Syntax
% set profiles adAttributeMapProfile <DEFAULT_AD_ATTRIBUTE_PROFILE > adAttributeList  <adAttribute> adAttributeName  <adAttributeName>


Command Parameters


adAttributeMapProfile Parameters

 Flexible ParameterLength/RangeDefaultDescriptionM/O
adAttributeMapProfile

NA

DEFAULT_AD_ATTRIBUTE_PROFILE

Ad attribute map profile name

M
adAttributeList1 - 32NAAd attribute sequence to be mapped with attribute nameM
adAttributeName1- 63NAAd attribute nameM

Command Example

The following is an example of how to create an AD Attribute Map Profile:


set profiles adAttributeMapProfile DEFAULT_AD_ATTRIBUTE_PROFILE adAttributeList adAttribute1 adAttributeName cn 
commit 
set profiles adAttributeMapProfile DEFAULT_AD_ATTRIBUTE_PROFILE adAttributeList adAttribute2 adAttributeName telephoneNumber 
commit 
set profiles adAttributeMapProfile DEFAULT_AD_ATTRIBUTE_PROFILE adAttributeList adAttribute3 adAttributeName mobile 
commit 
set profiles adAttributeMapProfile DEFAULT_AD_ATTRIBUTE_PROFILE adAttributeList adAttribute4 adAttributeName unixHomeDirectoryNumber 
commit

With the above configuration in the SBC, adAttribute1 refers to cn in all other entities like dmPm criteria, dmPm Rule and Call Parameter Filter Profile. Similarly adAttribute2 refers to telephoneNumber, and so on.

If any changes are made in this profile, and the data has already successfully synchronized before the modification, then perform a synchronization using either the manual sync command or wait until the syncInterval timer starts and synchronizes the data. Until synchronization is performed, the new modified data is not used, thus call failures can occur.


  • No labels