You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

In this section:

Related articles:

Profiles - Number Translation Criteria

Servers - CLI

Request System - CLI

Show Status System

Show Status Global

Number Translation Criteria - CLI

all Routing: System Provisioning - Profiles

Global - Servers

System - Admin

All - System 

Global - Policy Server

Profiles - Number Translation Criteria

The SBC Core is enhanced to support Flexible Active Directory functionality for large enterprises with a bigger subscriber base to provide a better call capacity solution.

In Enterprise deployments, the ERE retrieves the user information from the Microsoft Active directory database and uses it for call routing and policy decisions. This reduces the administrative overhead of provisioning and managing the user information at two places. The ERE retrieves the Subscriber information by querying the Active Directory database, which includes:

  • Subscriber Identity
  • Display name
  • Home phone number
  • Mobile phone number
  • Office/Lync phone number

Since LDAP is a known slow response protocol, the SBC fetches the data from the remote server and stores it in the local database instead of querying real time to the remote server. This data is later used during calls to manipulate various call parameters and use them in routing logic.

As explained above, for Flexible AD to work, the configurations are classified into two categories:

  1. Configuration to Sync Data from Remote Server
  2. Synced data use during call processing

Fetching AD Attributes from the AD Server

Fetching the Active Directory attributes involves the following:

  • The ERE provides a flexible option to fetch the dynamic AD attributes from the AD server and cached locally.
  • When the AD attributes are added or removed, the SBC-ERE fetches the new attributes from the AD server and stores them locally. This procedure does not require any process restarts or system down time.
  • The SBC-ERE normalizes (remove space and hyphens) the attribute value, if they are of telephone number format. For example, If the "mobile" AD attribute value is "714-555-5555", the SBC ERE removes the hyphens and store the mobile AD attribute value as "7145555555".
  • The SBC-ERE queries the AD server and updates the local cache when a new flexible AD attribute is configured.
  • The SBC-ERE supports a configuration of 32 flexible AD attributes.
  • Local AD query: The SBC provides a utility to query the locally-stored AD attributes and display the associated AD attributes. For example, The SBC-ERE has a tool/utility to query (only the configured AD attributes) the locally stored AD attributes and display the results.
  • The SBC queries the AD attributes that are dynamically configured, and the result displays all the AD attributes associated with the queried AD attribute.
  • The SBC-ERE continues processing the call in case the AD lookup / query fails.

DM/PM of AD Attributes

The SBC has a "Transformation Table" that performs number manipulations. This table is configured so that any of the parameters input in the table are modifiable using regular expression or replaced by values of any AD attributes. For example, an AD lookup is done on the Called Number. If it is a success, then the called number is modified to the value that is present in the "mobile" AD attribute or "msRTCSIP" AD attribute received in the AD lookup. Similarly, you can change the calling number to the "displayname" AD attribute. The DM/PM is enhanced to reflect the flex AD attributes that are configured at the SBC-ERE.

The flexible AD attributes are available to the DM/PM rules when AD service is invoked. This is applicable for both "In" and "Out" DM/PM.

Prior to this release, the pre-defined AD attributes in the SBC are available for DM/PM. With the SBC enhancement of flexible AD attributes, the dynamically configured AD attributes are also available for DM/PM.

Flexible AD Attributes for CPFP

The Flexible AD attributes for CPFP involves the following:

  • In addition to the pre-defined AD attributes, the flexible AD attributes are options are available at CPFP to influence the routing decisions.
  • The flexible AD attributes are dynamically available to CPFP for routing (for example; standard routing , username routing) decisions.
  • The SBC-ERE presents the complete calling number for outbound calls to the mobile subscriber who is a part of enterprise. This takes higher precedence than the other outbound calls requirements
  • The SBC-ERE uses the "UnixHomeDirectory" AD attribute, if present as the calling number for outbound calls.
  • The SBC-ERE uses a desired number as the calling number for outbound calls, if "UnixHomeDirectory" AD attribute is not available.
  • The SBC-ERE uses the "info" AD attribute, if present to route the call for the called number.
  • The SBC-ERE uses the "msRTCSIP" AD attribute if present to route the call for the called number, provided the "info" AD attribute is not available.
  • The SBC-ERE routes the call as per the existing routing mechanism if both "info" and "msRTCSIP" AD attributes are not preset for called number.
  • The SBC-ERE uses the management interface to query the AD server
  • The SBC-ERE supports VLAN tagging while communicating with the AD server.

Platform Changes

The Flexible AD functionality is applicable for SBC with ERE (SWe and hardware-based).

Capacity Changes

The SBC-ERE supports a minimum of 100,000 subscriber entries.

 

 

  • No labels