Geolocations

Geolocations
Civic Address
Devices are assigned a geolocation from either the device page, device pool, or default Geolocation under Enterprise Parameters, in that order of precedence.

GeoLocation filter
Controls what actual settings from the Geolocation are going to apply to the device and what attributes to apply the filter on

Logical Policy
Indicates whether a connection is permitted or denied
The configured policies work bidirectionally between the pair of devices

Logical Partitioning
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.

Devices are classified into two seperate elements; a border element or an interior element. Device Type is decided by system and cannot be change
Border

  • Gateway (for example, H.323 Gateway)
  • Intercluster 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, third party)
  • CTI route points
  • VG224 analog phones
  • MGCP port (FXS)
  • Cisco Unity Voice Mail (SCCP)

Logical policies can apply to:

  • Interior to Border
  • Border to Interior
  • Border to Border


Configuration

1]Enable Logical Partitioning enterprise parameter to True
2]Define a set of System > Geolocations
3]Assign geolocations to device pools, devices, trunks, gateways, or MGCP ports
4]Define the Logical Partitioning Default Policy, which determines whether to allow or deny PSTN calls between devices that associate with valid geolocations and geolocation filters when no explicit Allow/Deny policy is configured in the Logical Partitioning Policy Configuration window for the related geolocation policy records
5]For devices that do not participate in logical partitioning policy checks, define the geolocation as Unspecified or leave undefined
6]Define a set of filter rules in a new System > Geolocation Filter
7]Assign geolocation filters to device pools, trunks, intercluster trunks, gateways, or MGCP ports
8]Assign geolocation filter to the default filter that the Logical Partitioning Default Filter enterprise parameter specifies
9]Define a set of logical partitioning policy records Call Routing > Logical Partitioning Policy Configuration
10]Define a set of policies between geolocation policy record device-type pairs:
{{Geolocation Policy1, devType1}, {Geolocation Policy2,devType2}, policyValue}
11]To allow devices in different clusters to participate in logical partitioning policy checks, turn on location conveyance as follows:

  • Check the Send Geolocation Information check box in the intercluster trunk (ICT) or SIP trunk of the local cluster.
  • Check the Send Geolocation Information check box in the ICT or SIP trunk of the remote cluster.

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
2. 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.
3. 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.

Tags:

About Alexis Katsavras

Working as Freelance Cisco Unified Communications Consultant in the UK. www.NetPacket.co.uk