Posted by: Mudassir Ali | May 2, 2012

All About Geo Location Logical Partition Policy

Logical partitioning specifies a call control feature in CUCM that provides functionality, so communication between the following pairs of VoIP entities can be controlled:

1. A VoIP phone and a VoIP gateway
2. A VoIP gateway and another VoIP gateway
3. An intercluster trunk and a VoIP phone
4. An intercluster trunk and a VoIP gateway

The elements of logical partitioning include:
Device types, where phones are classified as interior, and gateways and trunks are defined as border. Below lists the endpoint types for different devices.
Geolocations, where endpoints are assigned a civic address to be used in policy decisions.
Geolocation filters, where policy decisions can be made on a subset of the geolocation objects.
Policies, where communications between endpoints are either allowed or denied based on their comparative (filtered) geolocations and device types.

Basic configuration:
· Enable Logical Partitioningà System>Enterprise Parameters >Logical Partitioning Default Policy (set this to true)
· System — Geo location
· System — Geo location filter
· Assign this location and filter to Device pool, gateway, ICT Trunk

Reference:
SRND Guide
Logical Partition
Troubleshooting Guide
Sample Configuration Guide PDF
How Cisco India Simplified VoIP and PSTN calls with Logical Partitioning for Cisco Unified Communications Manager
RFC4119

Geolocation Assignment:
Devices are assigned a geolocation from either the device page, the device pool, or the default Geolocation as configured under Enterprise Parameters, in that order of precedence.
Geolocation Filter Creation:
Geolocation filters define which of the geolocation objects should be used when comparing the geolocations of different endpoints. For example, a group of phones may be assigned identical geolocations, except for the room and floor in which they are located. Policies may want to consider endpoints located within the same building as being within the same Closed User Group, and thus allowed to communicate. Even though the actual geolocations of each phone differ, the filtered geolocation is the same. This is useful when policies need to be applied to only the top-level fields of geolocation. For instance, a policy that denies communications between phones and gateways in different cities but allows communications between phones and gateways in the same city, could be based on the comparative filtered geolocations where objects more granular than the City are ignored.

Geolocation Filter Assignment
Phones inherit the filter assignment of their device pool. Gateways and trunks can be configured with a geolocation filter at the device or device pool level, in that order of precedence.
Logical Partitioning Policy Configuration
Logical partitioning policies are configured between geolocation identifiers. A geolocation identifier is the combination of a filtered geolocation and a device type. The filtered geolocation is obtained by taking a device’s geolocation and applying the device’s associated geolocation filter.
A policy is created as the combination of a set of geolocation objects and a device type (a source geolocation identifier) in relationship with another such combination (the target geolocation identifier). When the relationship is matched, the configured action of "allow" or "deny" is applied to the call leg.

Logical Partitioning Device Types Cisco Unified Communications Manager Device
Border Gateway (for example, H.323 gateway)

Inter-luster trunk (ICT), both gatekeeper-controlled and non-gatekeeper-controlled
H.225 trunk
SIP trunk
MGCP port (E1, T1, PRI, BRI, FXO)

Interior Phones (SCCP, SIP, or third-party)

CTI route points
VG224 analog phones
MGCP port (FXS)
Cisco Unity voicemail (SCCP)

Cisco Unified Reporting can give you below details:
Unified CM GeoLocation Policy: Provides a list of records from the GeoLocation Logical Partitioning Policy Matrix.
Unified CM GeoLocation Policy with Filter: Provides a list of records from the GeoLocation Logical Partitioning Policy Matrix for the selected GeoLocation policy.

Cisco RTMT Tool: You can watch the status of logical partitions failure from RTMT Tool

Introducing Logical Partitioning

This slideshow requires JavaScript.

Note:
1. Policies are not applied if all participants in a call (or call attempt) are classified as interior. This means that calls between phones on the same cluster are never subjected to logical partitioning policies.
2. Geolocations are not to be confused with locations configured in Unified CM, which are used for call admission control, or with physical locations used for Device Mobility.
3. Each set of geolocation objects configured in a policy is considered in association with a single device type. For example, a set of geolocation objects such as Country=India, State=Karnataka, City=Bangalore needs to be associated with device type Interior for actions pertaining to Bangalore phones, and separately associated with device type Border for actions pertaining to Bangalore gateways.
4. When the geolocation identifiers of two devices are being evaluated by logical partitioning, no policy is applied if both devices are of device type Interior. This means that no call, conference, transfer, or so forth, between IP phones within the same cluster will ever be denied due to logical partitioning policies.
5. The default policy in Unified CM is deny; in other words, if no policy is configured explicitly to permit a call leg, the call leg will be denied.

Advertisements

Responses

  1. Thanks for the great writeup. I have been struggling over this for a while now with the single line LP. Partially successful
    1) Can restrict mid call joining for locations within india on VoIP with PSTN. 🙂
    2) Still CAN’T restrict a PSTN call in India joining of Bangalore VoIP phone > ICT (Gatekeeper controlled) US Cluster VoIP phone.
    I have followed your example PDF step by step but i can still not restrict those calls. Any ideas would be really helpful.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: