-
Cisco Unified Communications Manager Features and Services Guide, Release 8.0(1)
-
Index
-
Preface
-
Barge and Privacy
-
Cisco Call Back
-
Call Control Discovery
-
Call Display Restrictions
-
Call Park and Directed Call Park (Revised 04/21/2010)
-
Call Pickup
-
Call Throttling and the Code Yellow State
-
Calling Party Normalization (Revised 03/25/2010)
-
Cisco Extension Mobility
-
Cisco Extension Mobility Cross Cluster
-
Cisco Unified Communications Manager Assistant With Proxy Line Support
-
Cisco Unified Communications Manager Assistant With Shared Line Support
-
Cisco Unified Communications Manager Auto-Attendant
-
Cisco Unified Mobility (Revised 10/24/2011)
-
Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration
-
Cisco Web Dialer
-
Client Matter Codes and Forced Authorization Codes
-
Custom Phone Rings
-
Device Mobility
-
Do Not Disturb
-
External Call Control
-
External Call Transfer Restrictions
-
Geolocations and Location Conveyance
-
Hold Reversion
-
Hotline
-
Immediate Divert
-
Intercom
-
Internet Protocol Version 6 (IPv6)
-
Licensing
-
Local Route Groups
-
Logical Partitioning (Revised 05/09/2011)
-
Malicious Call Identification
-
Monitoring and Recording
-
Multilevel Precedence and Preemption
-
Music On Hold
-
Presence
-
Quality Report Tool
-
Feedback
Table Of Contents
Geolocations and Location Conveyance
Configuration Checklist for Geolocations
Configuration Checklist for Geolocation Filters
Configuration Checklist for Location Conveyance
Geolocation Usage for Shared Lines and Route Lists
Geolocation Configuration Settings
Introducing Geolocation Filters
Geolocation Filter Configuration
Configuring a Geolocation Filter
Geolocation Filter Configuration Settings
Introducing Location Conveyance
Geolocation Conveyance Across SIP Trunks and Intercluster Trunks
SIP Trunk Error Handling for Geolocation Information
Intercluster Trunk Error Handling for Geolocation Information
Handling a Received Geolocation
Feature Interactions with Midcall Geolocation Change
Location Conveyance Configuration
Geolocations and Location Conveyance
This chapter discusses the following concepts:
•
Geolocations
•
•
Tip
This chapter contains information on the following topics:
•
•
•
•
•
•
•
Configuration Checklist for Geolocations
Geographical location information, or geolocation, describes a physical position in the world that may correspond to the past, present, or future location of a person, event, or device.
Cisco Unified Communications Manager Administration allows you to specify a geolocation for every device.
The Request for Comments (RFC) 4119 standard provides the basis for geolocations. Geolocations use the civic location format that specifies the following fields: country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, and PC.
In Cisco Unified Communications Manager Administration, geolocations get configured manually.
Tip
Table 23-1 provides a checklist for configuring geolocations. For more information on geolocations, see the "Introducing Geolocations" section and the "Related Topics" section.
Table 23-1 Geolocation Configuration Checklist
Step 1
Define a set of geolocations on a new Geolocation Configuration window.
Step 2
Assign geolocations to device pools, devices, trunks, gateways, or MGCP ports.
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Displaying the MAC Address of a Phone, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Step 3
Assign geolocations to the default geolocation that the Default Geolocation enterprise parameter specifies.
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Step 4
For devices that do not participate in features that require geolocations, define the geolocation as Unspecified or leave undefined.
Note
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Displaying the MAC Address of a Phone, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Additional Information
See the "Related Topics" section.
Configuration Checklist for Geolocation Filters
Cisco Unified Communications Manager administrators define a geolocation filter for every device that participates in a feature that uses geolocation filters. Geolocation filters allow selection of specific fields from the 17 geolocation fields for the purpose of creating an identifier from the selected fields. Geolocation filters get configured manually.
Cisco Unified Communications Manager administrators then assign geolocation filters to devices.
Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters.
Table 23-2 provides a checklist for configuring geolocation filters. For more information on geolocation filters, see the "Introducing Geolocation Filters" section and the "Related Topics" section.
Table 23-2 Geolocation Configuration Checklist
Step 1
Define a set of filter rules in a new Geolocation Filter Configuration window.
Step 2
Assign geolocation filters to device pools, trunks, intercluster trunks, gateways, or MGCP ports.
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Step 3
For the logical partitioning feature, assign geolocation filter to the default filter that the Logical Partitioning Default Filter enterprise parameter specifies.
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Additional Information
See the "Related Topics" section.
Configuration Checklist for Location Conveyance
Location conveyance involves configuration to make the following behavior possible:
•
–
Note
For the logical partitioning feature in the current release, the Cisco Unified Communications Manager does not send the configured geolocation information to line devices (phones that are running SIP or SCCP).Table 23-3 provides a checklist for configuring location conveyance in a multicluster logical partitioning environment.
Table 23-3 Location Conveyance Configuration Checklist
Step 1
Define a set of geolocations in a new Geolocation Configuration window.
Step 2
Assign geolocations to device pools, devices, SIP trunks, intercluster trunks, gateways, or MGCP ports for the devices that need to participate in location conveyance.
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Displaying the MAC Address of a Phone, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Step 3
Assign geolocations to a default geolocation that the Default Geolocation enterprise parameter specifies.
This assignment allows you to specify a default geolocation for a cluster.
For devices for which no associated geolocation exists at the device or device-pool level, the value that is specified by the Default Geolocation enterprise parameter applies.
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Step 4
If geolocation information about devices needs to be communicated across clusters, ensure that location conveyance is configured.
To do so, check the Send Geolocation Information check box in the intercluster trunk (ICT) or SIP trunk for the devices that need to pass geolocation information across clusters as follows:
•
•
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Additional Information
See the "Related Topics" section.
Introducing Geolocations
Geographical location information, or geolocation, describes a physical position in the world that may correspond to the past, present, or future location of a person, event, or device.
Cisco Unified Communications Manager Administration allows you to specify a geolocation for every device.
The Request for Comments (RFC) 4119 standard provides the basis for geolocations. Geolocations use the civic location format that specifies the following fields: country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, and PC.
In Cisco Unified Communications Manager Administration, geolocations get configured manually.
Tip
Additional Information
See the "Related Topics" section.
Overview of Geolocations
Configuration of geolocations entails provisioning the following elements:
•
–
–
–
Additional Information
See the "Related Topics" section.
Geolocation Characteristics
Cisco Unified Communications Manager administrators must define the following item:
•
Cisco Unified Communications Manager administrators then assign geolocations to devices.
The following entities in a Cisco Unified Communications Manager cluster can have geolocation and geolocation filter values that are assigned:
•
•
•
•
Note
•
•
•
•
You do not need to associate media devices, such as media termination points (MTP), conference bridges (CFB), annunciators, and music on hold (MOH) servers, with geolocations.
Internally, the device layer of Cisco Unified Communications Manager associates with geolocation values that call processing uses. The following sequence takes place:
1.
2.
3.
4.
Source of Geolocation Information
The following logic determines the geolocation value:
1.
2.
3.
4.
5.
The standard record for a geolocation specifies Unspecified. Use this value when no geolocation needs to associate with a device. In such scenarios, any features that are based on geolocations do not execute. Also, devices for which no geolocation gets specified do not participate in geolocation information conveyance across clusters for intercluster calls.
Be aware that the Default Geolocation enterprise parameter can be configured from drop-down list boxes on the Enterprise Parameters Configuration window.
Additional Information
See the "Related Topics" section.
Geolocation Usage for Shared Lines and Route Lists
When the called party specifies a group device, a different geolocation can apply for each device in a group. For the early attended scenarios, you do not know the actual connected device until the device gets answered. Thus, the Geolocation information gets aggregated until the device answers.
•
•
Geolocation Examples
Table 23-4 specifies examples of geolocations.
Additional Information
See the "Related Topics" section.
Geolocation Identifiers
Geolocation identifiers get constructed from a combination of geolocations, geolocation filters, and device types of Cisco Unified Communications Manager devices.
See the following sections for detailed descriptions of geolocations and geolocation filters:
•
•
Geolocation filters allow selection of specific fields from the 17 geolocation fields. Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters manually. Specific Cisco Unified Communications Manager features associate the geolocation filters by using drop-down list boxes in the configuration windows of the devices that get configured for a particular feature.
The Cisco Unified Communications Manager device type of a device specifies one of the following values:
•
•
Refer to Table 31-2 in the "Logical Partitioning" chapter for a detailed listing of the Cisco Unified Communications Manager devices that associate with the Border and Interior device types.
The following object specifies an example geolocation identifier:
{geolocPkid=9dc76052-3a37-78c2-639a-1c02e8f5d3a2, filterPkid=d5bdda76-6a86-56c5-b5fd-6dff82b37493, geolocVal=, devType=8}
where:
The geolocVal field gets used in cases where the Cisco Unified Communications Manager database does not reference the geolocation record but data for a geolocation comes from another source (for example, location conveyance PIDF-LO XML from a remote cluster).
In such cases, Cisco Unified Communications Manager constructs the name value pair for the geolocation fields.
Example: "country=US:A1=Texas:A3=Richardson:LOC=Building 6" where the value gets communicated through the geolocVal field.
Note
The following string specifies the logical representation of a geolocation identifier:
"Border:country=US:A1=Texas:A3=Richardson:LOC=Building 6"
Note
Additional Information
See the "Related Topics" section.
Geolocation Interactions
The following interaction applies to geolocations:
•
Refer to the "Introducing Location Conveyance" section for a detailed discussion of location conveyance.
Additional Information
See the "Related Topics" section.
Geolocation Configuration
Tip
Use the System > Geolocation Configuration menu option in Cisco Unified Communications Manager Administration to configure geolocations.
Tip
To configure geolocations, see the following sections:
•
Additional Information
See the "Related Topics" section.
Finding a Geolocation
Because you might have multiple geolocations in your network, Cisco Unified Communications Manager lets you search for geolocations on the basis of specified criteria. Follow these steps to search for a specific geolocations in the Cisco Unified Communications Manager database.
Note
Procedure
Step 1
The Find and List Geolocations window displays. Records from an active (prior) query may also display in the window.
Step 2
To filter or search records
•
•
•
Note
Step 3
All matching records display. You can change the number of items that display by choosing a different value from the Rows per Page drop-down list box.
Note
Step 4
Note
The window displays the item that you choose.
Additional Information
See the "Related Topics" section.
Configuring a Geolocation
Perform the following procedure to add or update a geolocation.
Procedure
Step 1
The Find and List Geolocations window displays.
Step 2
•
The Geolocation Configuration window displays.
•
Step 3
Step 4
If you added a geolocation, the list box at the bottom of the window now includes the new geolocation.
Additional Information
See the "Related Topics" section.
Deleting a Geolocation
Perform the following procedure to delete an existing geolocation.
Procedure
Step 1
The Find and List Geolocations window displays.
Step 2
A list of geolocations that match the search criteria displays.
Step 3
•
•
•
A confirmation dialog displays.
Step 4
The specified geolocation gets deleted.
Additional Information
See the "Related Topics" section.
Geolocation Configuration Settings
Geographical location information, or geolocation, describes a physical position in the world that may correspond to the past, present, or future location of a person, event, or device.
Cisco Unified Communications Manager Administration allows you to specify a geolocation for every device.
In Cisco Unified Communications Manager Administration, geolocations get configured manually.
Tip
Table 23-5 describes the configuration settings that are used for configuring geolocations.
Additional Information
See the "Related Topics" section.
Introducing Geolocation Filters
Cisco Unified Communications Manager administrators define the following item:
•
Cisco Unified Communications Manager administrators then assign geolocation filters to devices.
The following logic determines the geolocation filter value:
1.
2.
3.
4.
Geolocation Filter Examples
Table 23-6 specifies examples of geolocation filters.
Additional Information
See the "Related Topics" section.
Geolocation Filter Configuration
Tip
Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters.
To configure geolocation filters, see the following sections:
•
•
•
Additional Information
See the "Related Topics" section.
Finding a Geolocation Filter
Because you might have multiple geolocation filters in your network, Cisco Unified Communications Manager lets you search for geolocation filters on the basis of specified criteria. Follow these steps to search for a specific geolocation filters in the Cisco Unified Communications Manager database.
Note
Procedure
Step 1
The Find and List Geolocation Filters window displays. Records from an active (prior) query may also display in the window.
Step 2
To filter or search records
•
•
•
Note
Step 3
All matching records display. You can change the number of items that display by choosing a different value from the Rows per Page drop-down list box.
Note
Step 4
Note
The window displays the item that you choose.
Additional Information
See the "Related Topics" section.
Configuring a Geolocation Filter
Perform the following procedure to add or update a geolocation filter.
Procedure
Step 1
The Find and List Geolocation Filters window displays.
Step 2
•
The Geolocation Filter Configuration window displays.
•
Step 3
Step 4
If you added a geolocation filter, the list box at the bottom of the window now includes the new geolocation filter.
Additional Information
See the "Related Topics" section.
Deleting a Geolocation Filter
Perform the following procedure to delete an existing geolocation filter.
Procedure
Step 1
The Find and List Geolocation Filters window displays.
Step 2
A list of geolocation filters that match the search criteria displays.
Step 3
•
•
•
A confirmation dialog displays.
Step 4
The specified geolocation filter gets deleted.
Additional Information
See the "Related Topics" section.
Geolocation Filter Configuration Settings
Cisco Unified Communications Manager administrators define the following item:
•
Cisco Unified Communications Manager administrators then assign geolocation filters to devices.
Table 23-7 describes the configuration settings that are used for configuring geolocation filters.
Additional Information
See the "Related Topics" section.
Introducing Location Conveyance
Location conveyance involves configuration to make the following behavior possible:
•
–
Note
For the logical partitioning feature in the current release, the Cisco Unified Communications Manager does not send the configured geolocation information to line devices (phones that are running SIP or SCCP).This section covers the following topics:
•
•
•
•
•
Additional Information
See the "Related Topics" section.
Geolocation Conveyance Across SIP Trunks and Intercluster Trunks
Geolocation conveyance entails the following characteristics:
•
•
The SIP trunk supports the location conveyance of Presence Information Data Format Location Object (PIDF-LO) as RFC 4119 describes, which specifies an encapsulation of location information within a presence document:
•
•
•
•
•
Intercluster trunk also supports location conveyance that is using PIDF-LO XML with reduction in some of the XML elements:
•
•
The SIP trunk or intercluster trunk uses the geolocation information and device type that the call control messages send to construct the PIDF-LO XML.
Additional Information
See the "Related Topics" section.
SIP Trunk Error Handling for Geolocation Information
Incoming requests that carry geolocation information for location conveyance get checked for compliance as follows:
1.
2.
3.
The SIP trunk that receives a noncompliant SIP request responds with a "424 Bad Location Information" response.
The following cases result in ignoring the processing of geolocation info. For information purposes, the SIP trunk sends a Geolocation-Error header in the next outgoing SIP response (for example, 180 or 200).
•
•
Because the received geolocation information gets ignored, the SIP trunk continues to use the locally configured geolocation information on the SIP trunk.
Additional Information
See the "Related Topics" section.
Intercluster Trunk Error Handling for Geolocation Information
If an error occurs while the received geolocation information on an intercluster trunk is being processed, locally configured geolocation information for the trunk gets used.
Additional Information
See the "Related Topics" section.
Handling a Received Geolocation
The cluster that receives the PIDF-LO XML parses the received geolocation information and passes the information as colon-separated name value pairs in the GeolocationInfo data structure of the CcNotifyInd signal.
Example: "Country=US:A1=NC:A3=RTP:LOC=BLD9"
The content of the received geolocation information of the PIDF-LO overrides any locally configured geolocation information on a trunk, which gets used for the device across the trunk.
Example: {geolocPkid=, filterPkid=d5bdda76-6a86-56c5-b5fd-6dff82b37493, geolocVal="Country=US:A1=NC:A3=RTP:LOC=BLD9", devType=4}
Additional Information
See the "Related Topics" section.
Feature Interactions with Midcall Geolocation Change
Outgoing Geolocation Change
The supplementary service (SS) feature interactions, such as Transfer, Conference, Park retrieval, and others, result in connected party change.
For such scenarios, if the SIP trunk or intercluster trunk device receives valid geolocation information from Call Control that differs from previously sent geolocation information, updated geolocation information gets communicated in an UPDATE (SIP trunk) or Notify (intercluster trunk) message.
Incoming Geolocation Change
For SS feature interactions in a remote cluster, the updated geolocation information gets received over an SIP trunk or intercluster trunk in an UPDATE or Notify message.
When such an update is received, the SIP trunk or intercluster trunk parses the PIDF-LO and passes the PIDF-LO to call control and to the LPSession process.
Example PIDF-LO
The following example shows a PIDF-LO that is sent across a SIP trunk. Be aware that the items that are shown in bold font are relevant for location conveyance.
UPDATE sip:4400@10.10.10.2:5060;transport=tcp SIP/2.0Date: Sat, 12 Jul 2008 13:28:42 GMTCall-Info: <urn:x-cisco-remotecc:callinfo>; security= NotAuthenticatedGeolocation: <cid:4900@10.10.10.1>;inserted-by="10.10.10.1"Content-ID: 4900@10.10.10.1From: <sip:4900@10.10.10.1>;tag=4d1edcb1-f546-4ee7-966c-2973fbc56475-31638661P-Asserted-Identity: <sip:4900@10.10.10.1>Content-Length: 1070User-Agent: Cisco-CUCM7.1To: <sip:4400@10.10.10.2>;tag=e1258ce2-8620-4005-9aa1-72d99cd54050-31642615Contact: <sip:4900@10.10.10.1:5060;transport=tcp>Content-Type: application/pidf+xmlCall-ID: bbb3f900-8781b563-b-47f54c0a@10.10.10.2Via: SIP/2.0/TCP 10.10.10.1:5060;branch=z9hG4bK179f431e3CSeq: 101 UPDATEMax-Forwards: 70<?xml version="1.0" encoding="UTF-8"?><presence xmlns="urn:ietf:params:xml:ns:pidf"xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"xmlns:cl=" urn:ietf:params:xml:ns:pidf:geopriv10:civicLoc"xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"xmlns:caps="urn:ietf:params:xml:ns:pidf:caps"xmlns:cisco="http://www.cisco.com"entity="pres:geotarget@example.com"><dm:device id="sg89ae"><caps:devcaps><cisco:gateway>false</cisco:gateway></caps:devcaps><gp:geopriv><gp:location-info><cl:civicAddress><cl:country>IN</cl:country><cl:A1>KA</cl:A1><cl:A2>a2</cl:A2><cl:A3>BLR</cl:A3><cl:A4>a4</cl:A4><cl:A5>a5</cl:A5><cl:A6>a6</cl:A6><cl:PRD>prd</cl:PRD><cl:POD>pod</cl:POD><cl:STS>sts</cl:STS><cl:HNO>123</cl:HNO><cl:HNS>hns</cl:HNS><cl:LMK>lmk</cl:LMK><cl:LOC>BLDG1</cl:LOC><cl:FLR>flr</cl:FLR><cl:NAM>nam</cl:NAM><cl:PC>pc</cl:PC></cl:civicAddress></gp:location-info><gp:usage-rules><gp:retransmission-allowed>yes</gp:retransmission-allowed><gp:retention-expiry>2008-09-03T17:58:19Z</gp:retention-expiry></gp:usage-rules></gp:geopriv><timestamp>2008-09-02T17:58:19Z</timestamp></dm:device></presence>Additional Information
See the "Related Topics" section.
Location Conveyance Configuration
If geolocation information about devices needs to be communicated across clusters, ensure that location conveyance is configured. To configure location conveyance, follow the steps that Table 23-3 provides.
To associate devices with geolocations, refer to the "Configuration Checklist for Geolocations" section.
Tip
Additional Information
See the "Related Topics" section.
Related Topics
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Additional Cisco Documentation
•
•
•
•
•
•
•
•
•
•
