Device Pool Settings
|
Device Pool Name
|
Enter the name of the new device pool that you are creating.
You can enter up to 50 characters, which include alphanumeric characters,
periods (.), hyphens (-), underscores (_), and blank spaces.
|
Cisco Unified Communications Manager Group
|
Choose the
Cisco Unified Communications Manager group to assign to
devices in this device pool. A
Cisco Unified Communications Manager group specifies a
prioritized list of up to three
Cisco Unified Communications Managers. The first
Cisco Unified Communications Manager in the list serves
as the primary
Cisco Unified Communications Manager for that group,
and the other members of the group serve as backup
Cisco Unified Communications Managers for redundancy.
|
Calling Search Space for Auto-registration
|
Choose the calling search space to assign to devices in this
device pool that auto-register with
Cisco Unified Communications Manager. The calling
search space specifies partitions that devices can search when attempting to
complete a call.
|
Adjunct CSS
|
From the drop-down list box, choose an existing Calling Search
Space (CSS) to use for the devices in this device profile as an adjunct CSS for
the Extension Mobility Cross Cluster (EMCC) feature. (To configure a new CSS or
modify an existing CSS, choose
in
Cisco Unified Communications Manager Administration.)
Default value specifies None.
When configuring the EMCC feature, the administrator must
configure a device pool for each remote cluster. If the remote cluster is
located in a different country, the adjunct CSS must embrace the partition with
which the emergency patterns of that country associate. This configuration
facilitates country-specific emergency call routing.
For more information about the adjunct CSS, see topics related
to EMCC call routing in the
Cisco Unified Communications Manager Features and Services Guide.
|
Reverted Call Focus Priority
|
Choose a clusterwide priority setting for reverted calls that
are invoked by the hold reversion feature. This setting specifies which call
type, incoming calls or reverted calls, have priority for user actions, such as
going off hook.
- Default—If you
choose this option, incoming calls have priority.
- Highest—If you
choose this option, reverted calls have priority.
The Not Selected setting specifies the reverted call focus
priority setting for the default device pool at installation. At installation,
incoming calls have priority. You cannot choose this setting in
Cisco Unified Communications Manager Administration.
Note
|
This setting applies specifically to hold reverted calls; it
does not apply to parked reverted calls.
|
For more information, see topics related to hold reversion in
the
Cisco Unified Communications Manager Features and Services Guide.
|
Intercompany Media
Services Enrolled Group
|
Select an Intercompany Media Services Enrolled Group from the drop-down list.
For more information, see the Cisco Intercompany Media Engine Installation and Configuration Guide.
|
Local Route Group Settings
The Local Route Group Settings enables you to associate the route groups that you add under with the local route groups that you configure on the Local Route Group Names window for any particular device pool.
To associate a route group with the local route group for any particular device pool, choose the relevant route group from
the drop-down list box. Select the default
value <None> to prevent implementation of the Local Route Group feature.
Note
|
The Standard Local Route Group entry on the left is a default field entry which is populated from pre-10.0(1) release input.
This field name may vary depending on the local route group name that you specify in the Local Route Group Names window under
menu path in Cisco Unified Communications Manager Administration. You can add multiple local route group names in the Local Route Group Names window. The Local Route Group Settings window
will display them as noneditable fields.
|
Tip
|
To configure the local route group names in the Local Route Group Names window, use the menu path in Cisco Unified Communications Manager Administration.
|
You can define site-specific local route groups (like primary local route group, secondary local route group, tertiary local
route group, and so on) when you configure multiple local route groups under .
For example, you can add multiple local route groups such as Emergency Route Group, Primary Local Route Group (for site A),
Secondary Local Route Group (for site A), Primary Local Route Group (for site B), and Secondary Local Route Group (for site
B). The Local Route Group feature enables you to specify different route groups for each site
(site A and site B) for the respective device pool. Also, you can define a separate call routing option for emergency calls
when you associate the Emergency Route Group with a different route group. Hence you can easily define separate call routing
options for emergency calls and PSTN calls.
See
the
Cisco Unified Communications Manager Features and Services Guide for additional information about Local Route Group feature.
|
Roaming Sensitive Settings
|
Date/Time Group
|
Choose the date/time group to assign to devices in this device
pool. The date/time group specifies the time zone and the display formats for
date and time.
|
Region
|
Choose the
Cisco Unified Communications Manager region to assign
to devices in this device pool. The
Cisco Unified Communications Manager region settings
specify voice codec that can be used for calls within a region and between
other regions.
|
Media Resource Group List
|
From the drop-down list box, choose a media resource group
list. A media resource group list specifies a prioritized list of media
resource groups. An application selects the required media resource (for
example, a music on hold server, transcoder, or conference bridge) from the
available media resource groups according to the priority order that is defined
in a media resource group list.
|
Location
|
Use locations to implement call admission control (CAC) in a
centralized call-processing system. CAC enables you to regulate audio quality
and video availability by limiting the amount of bandwidth that is available
for audio and video calls over links between locations. The location specifies
the total bandwidth that is available for calls to and from this location.
From the drop-down list box, choose the appropriate location
for this device pool.
A location setting of None or Hub_None means that the
locations feature does not keep track of the bandwidth that the devices in this
device pool consume. A location setting of Phantom specifies a location that
enables successful CAC across intercluster trunks that use H.323 protocol or
SIP.
To configure a new location, use the
menu option.
For an explanation of location-based CAC across intercluster
trunks, see topics related to location-based CAC in the
Cisco Unified Communications Manager System Guide.
|
Network Locale
|
From the drop-down list box, choose the locale that is
associated with phones and gateways. The network locale contains a definition
of the tones and cadences that the phones and gateways in the device pool in a
specific geographic area use. Make sure that you select a network locale that
is supported by all of the phones and gateways that use this device pool.
Note
|
If the user does not choose a network locale, the locale
that is specified in the
Cisco Unified Communications Manager clusterwide
parameters as Default Network Locale applies.
|
Note
|
Choose only a network locale that is already installed and
supported by the associated devices. The list contains all available network
locales for this setting, but not all are necessarily installed. If a device is
associated with a network locale that it does not support in the firmware, the
device will fail to come up.
|
|
SRST Reference
|
From the drop-down list box, choose a survivable remote site
telephony (SRST) reference to assign to devices in this device pool. Choose
from the following options:
- Disable—If you
choose this option, devices in this device pool will not have SRST reference
gateways that are available to them.
- Use Default
Gateway—If you choose this option, devices in this device pool use the default
gateway for SRST.
- Existing SRST
references—If you choose an SRST reference from the drop-down list, devices in
this device pool will use this SRST reference gateway.
|
Connection Monitor Duration
|
This setting defines the time that the
Cisco Unified IP Phone monitors its connection to
Cisco Unified Communications Manager before it
unregisters from SRST and reregisters to
Cisco Unified Communications Manager.
To use the configuration for the enterprise parameter, you can
enter -1 or leave the field blank. The default value for the enterprise
parameter equals 120 seconds.
Change this setting if you need to disable the connection
monitor or if you want to extend the connection monitor time. The maximum
number of seconds that you can enter in the field equals 2592000.
Tip
|
When you change the value of the connection
monitor duration, it applies only to the device pool that is being updated. All
other device pools use the value in their own connection monitor duration
fields or use the value that is configured in the enterprise parameter.
|
For more information, see topics related to survivable remote
site telephony in the
Cisco Unified Communications Manager System Guide.
|
Single Button Barge
|
This setting determines whether the devices or phone users in
this device pool have single-button access for barge and cBarge. From the
drop-down list box, choose from the following options:
- Off—If you choose
this option, the devices in this device pool will have the Single Button
Barge/cBarge feature disabled.
- Barge—If you
choose this option, the devices in this device pool will have the Single Button
Barge feature enabled.
- CBarge—If you
choose this option, the devices in this device pool will have the Single Button
cBarge feature enabled.
- Default—If you
choose this option, the devices in this device pool will use the service
parameter setting for the Single Button Barge/cBarge feature.
|
Join Across Lines
|
This setting determines whether the Join Across Lines feature
is enabled for the devices or phone users in this device pool. From the
drop-down list box, choose from the following options:
- Off—If you choose
this option, the devices in this device pool will have the Join Across Lines
feature disabled.
- On—If you choose
this option, the devices in this device pool will have the Join Across Lines
feature enabled.
- Default—If you
choose this option, the devices in this device pool will use the service
parameter setting for the Join Across Lines feature.
|
Physical Location
|
Select the physical location for this device pool. The system
uses physical location with the device mobility feature to identify the
parameters that relate to a specific geographical location.
|
Device Mobility Group
|
Device mobility groups represent the highest level geographic
entities in your network and are used to support the device mobility feature.
|
Wireless LAN Profile Group
|
Select a wireless LAN profile group from the drop-down list box. You may also click View Details to display the settings for this wireless LAN profile group.
Note
|
You can specify the Wireless LAN Profile Group at the Device Pool level or the individual phone level.
|
|
Wi-Fi Hotspot Profile
|
Select a Wi-Fi Hotspot Profile from the drop-down list box. You may also click View Details to display details about the Wi-Fi Hotspot Profile that you select.
|
Device Mobility Related Information
|
Device Mobility Calling Search Space
|
Choose the appropriate calling search space to be used as the
device calling search space when the device is roaming and in same device
mobility group.
|
AAR Calling Search Space
|
Choose the appropriate calling search space for the device to
use when automated alternate routing (AAR) is performed. The AAR calling search
space specifies the collection of route partitions that are searched to
determine how to route a collected (originating) number that is otherwise
blocked due to insufficient bandwidth.
|
AAR Group
|
Choose the automated alternate routing (AAR) group for this
device. The AAR group provides the prefix digits that are used to route calls
that are otherwise blocked due to insufficient bandwidth. An AAR group setting
of None specifies that no rerouting of blocked calls will be attempted.
|
Calling Party Transformation CSS
|
This setting allows you to localize the calling party number
on the device. Make sure that the Calling Party Transformation CSS that you
choose contains the calling party transformation pattern that you want to
assign to this device pool.
Tip
|
Before the call occurs, the device must apply
the transformation by using digit analysis. If you configure the Calling Party
Transformation CSS as None for the device pool and you check the Use Device
Pool Calling Party Transformation CSS check box in the device configuration
window, the transformation does not match and does not get applied. Ensure that
you configure the Calling Party Transformation Pattern in a non-null partition
that is not used for routing.
|
|
Called Party Transformation CSS
|
This setting allows you to localize the called party number on
the device. Make sure that the Called Party Transformation CSS that you choose
contains the called party transformation pattern that you want to assign to
this device pool.
Note
|
If you configure the Called Party Transformation CSS as
None, the transformation does not match and does not get applied. Ensure that
you configure the Called Party Transformation pattern in a non-null partition that
is not used for routing.
|
|
Geolocation Configuration
|
Geolocation
|
From the drop-down list box, choose a geolocation.
You can choose the Unspecified geolocation, which designates
that the devices in this device pool do not associate with a geolocation.
You can also choose a geolocation that has been configured
with the
menu option.
For an explanation of geolocations, including configuration
details, see topics related to geolocations and location conveyance in the
Cisco Unified Communications Manager Features and Services Guide.
For an overview and details of how logical partitioning uses
geolocations, see topics related to geolocations and location conveyance in the
Cisco Unified Communications Manager Features and Services Guide.
|
Geolocation Filter
|
From the drop-down list box, choose a geolocation filter.
If you leave the <None> setting, no geolocation filter
gets applied for the devices in this device pool.
You can also choose a geolocation filter that has been
configured with the
menu option.
For an explanation of geolocation filters, including
configuration details, see the
Cisco Unified Communications Manager Features and Services Guide.
For an overview and details of how logical partitioning uses
geolocation filters, see the
Cisco Unified Communications Manager Features and Services Guide.
|
Incoming Calling Party Settings
|
Clear Prefix Settings
|
To delete all prefixes for all calling party number types,
click Clear Prefix Settings.
|
Default Prefix Settings
|
To enter the default value for all prefix fields at the same
time, click Default Prefix Settings.
|
National Number
|
Configure the following settings to globalize calling party
numbers that use National for the Calling Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to calling
party numbers that use National for the Calling Party Numbering Type. You can
enter up to 8 characters, which include digits, the international escape
character (+), asterisk (*), or the pound sign (#). You can enter the word,
Default, instead of entering a prefix.
If the word, Default, displays in the Prefix field,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming calling party prefix, which
supports both the prefix and strip digit functionality.
- Strip Digits—Enter
the number of digits, up to the number 24, that you want
Cisco Unified Communications Manager to strip from the
calling party number of National type before it applies the prefixes.
- Calling Search
Space—This setting allows you to globalize the calling party number of National
calling party number type on the device. Make sure that the calling search
space that you choose contains the calling party transformation pattern that
you want to assign to this device.
Before the call occurs, the device must apply the
transformation by using digit analysis. If you configure the CSS as None, the
transformation does not match and does not get applied. Ensure that you
configure the calling party transformation pattern in a non-null partition that
is not used for routing.
Tip
|
For more information on configuring these
settings, see topics related to configuring incoming calling party settings for
a device pool, gateway, or trunk in the
Cisco Unified Communications Manager Features and Services Guide.
|
|
International Number
|
Configure the following settings to globalize calling party
numbers that use International for the Calling Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to calling
party numbers that use International for the Calling Party Numbering Type. You
can enter up to 8 characters, which include digits, the international escape
character (+), asterisk (*), or the pound sign (#). You can enter the word,
Default, instead of entering a prefix.
If the word, Default, displays in the Prefix field in the
Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming calling party prefix, which
supports both the prefix and strip digit functionality.
- Strip Digits—Enter
the number of digits, up to the number 24, that you want
Cisco Unified Communications Manager to strip from the
calling party number of International type before it applies the prefixes.
- Calling Search
Space—This setting allows you to globalize the calling party number of
International calling party number type on the device. Make sure that the
calling party transformation CSS that you choose contains the calling party
transformation pattern that you want to assign to this device.
Before the call occurs, the device must apply the
transformation by using digit analysis. If you configure the CSS as None, the
transformation does not match and does not get applied. Ensure that you
configure the calling party transformation pattern in a non-null partition that
is not used for routing.
Tip
|
For more information on configuring these
settings, see topics related to configuring incoming calling party settings for
a device pool, gateway, or trunk in the
Cisco Unified Communications Manager Features and Services Guide.
|
|
Unknown Number
|
Configure the following settings to globalize calling party
numbers that use Unknown for the Calling Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to calling
party numbers that use Unknown for the Calling Party Numbering Type. You can
enter up to 8 characters, which include digits, the international escape
character (+), asterisk (*), or the pound sign (#).
If the word, Default, displays in the Prefix field in the
Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming calling party prefix, which
supports both the prefix and strip digit functionality.
- Strip Digits—Enter
the number of digits, up to the number 24, that you want
Cisco Unified Communications Manager to strip from the
calling party number of Unknown type before it applies the prefixes.
- Calling Search
Space—This setting allows you to globalize the calling party number of Unknown
calling party number type on the device. Make sure that the calling party
transformation CSS that you choose contains the calling party transformation
pattern that you want to assign to this device.
Before the call occurs, the device must apply the
transformation by using digit analysis. If you configure the CSS as None, the
transformation does not match and does not get applied. Ensure that you
configure the calling party transformation pattern in a non-null partition that
is not used for routing.
Tip
|
For more information on configuring these
settings, see topics related to configuring incoming calling party settings for
a device pool, gateway, or trunk in the
Cisco Unified Communications Manager Features and Services Guide.
|
|
Subscriber Number
|
Configure the following settings to globalize calling party
numbers that use Subscriber for the Calling Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to calling
party numbers that use Subscriber for the Calling Party Numbering Type. You can
enter up to 8 characters, which include digits, the international escape
character (+), asterisk (*), or the pound sign (#).
If the word, Default, displays in the Prefix field in the
Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming calling party prefix, which
supports both the prefix and strip digit functionality.
- Strip Digits—Enter
the number of digits, up to the number 24, that you want
Cisco Unified Communications Manager to strip from the
calling party number of Subscriber type before it applies the prefixes.
- Calling Search
Space—This setting allows you to globalize the calling party number of
Subscriber calling party number type on the device. Make sure that the CSS that
you choose contains the calling party transformation pattern that you want to
assign to this device.
Before the call occurs, the device must apply the
transformation by using digit analysis. If you configure the CSS as None, the
transformation does not match and does not get applied. Ensure that you
configure the calling party transformation pattern in a non-null partition that
is not used for routing.
Tip
|
For more information on configuring these
settings, see topics related to configuring incoming calling party settings for
a device pool, gateway, or trunk in the
Cisco Unified Communications Manager Features and Services Guide.
|
|
Incoming Called Party Settings
The Incoming Called Party Settings support H.323 trunks and
gateways. The H.323 protocol does not support the international escape
character +. To ensure the correct prefixes, including the +, get applied to
inbound calls over H.323 gateways/trunks, configure the incoming called party
settings; that is, configuring the incoming called party settings ensures that
when an inbound call comes from a H.323 gateway or H.323 trunk,
Cisco Unified Communications Manager transforms the
called party number back to the value that was originally sent over the
trunk/gateway.
|
Clear Prefix Settings
|
To delete all prefixes for all called party number types,
click Clear Prefix Settings.
|
Default Prefix Settings
|
To enter the default value for all prefix fields at the same
time, click Default Prefix Settings.
|
National Number
|
Configure the following settings to transform incoming called
party numbers that use National for the Called Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called
party numbers that use National for the Called Party Numbering Type. You can
enter up to 16 characters, which include digits, the international escape
character (+), asterisk (*), or the pound sign (#). You can enter the word,
Default, instead of entering a prefix.
Tip
|
If the word, Default, displays in the Prefix
field in the Gateway or Trunk Configuration window, you cannot configure the
Strip Digits field in the Gateway or Trunk Configuration window. In this case,
Cisco Unified Communications Manager takes the
configuration for the Prefix and Strip Digits fields from the device pool that
is applied to the device. If the word, Default, displays in the Prefix field in
the Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming called party prefix, which
supports both the prefix and strip digit functionality.
|
Tip
|
To configure the Strip Digits field, you
must leave the Prefix field blank or enter a valid configuration in the Prefix
field. To configure the Strip Digits fields, do not enter the word, Default, in
the Prefix field.
|
- Strip Digits—Enter
the number of digits that you want Cisco Unified Communications Manager to
strip from the called party number of National type before it applies the
prefixes.
- Calling Search
Space—This setting allows you to transform the called party number of National
called party number type on the device. If you choose None, no transformation
occurs for the incoming called party number. Make sure that the calling search
space that you choose contains the called party transformation pattern that you
want to assign to this device.
|
International Number
|
Configure the following settings to transform incoming called
party numbers that use International for the Called Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called
party numbers that use International for the Called Party Numbering Type. You
can enter up to 16 characters, which include digits, the international escape
character (+), asterisk (*), or the pound sign (#). You can enter the word,
Default, instead of entering a prefix.
Tip
|
If the word, Default, displays in the Prefix
field in the Gateway or Trunk Configuration window, you cannot configure the
Strip Digits field in the Gateway or Trunk Configuration window. In this case,
Cisco Unified Communications Manager takes the
configuration for the Prefix and Strip Digits fields from the device pool that
is applied to the device. If the word, Default, displays in the Prefix field in
the Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming called party prefix, which
supports both the prefix and strip digit functionality.
|
Tip
|
To configure the Strip Digits field, you
must leave the Prefix field blank or enter a valid configuration in the Prefix
field. To configure the Strip Digits fields, do not enter the word, Default, in
the Prefix field.
|
- Strip Digits—Enter
the number of digits that you want Cisco Unified Communications Manager to
strip from the called party number of International type before it applies the
prefixes.
- Calling Search
Space—This setting allows you to transform the called party number of
International called party number type on the device. If you choose None, no
transformation occurs for the incoming called party number. Make sure that the
calling search space that you choose contains the called party transformation
pattern that you want to assign to this device.
|
Unknown Number
|
Configure the following settings to transform incoming called
party numbers that use Unknown for the Called Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called
numbers that use Unknown for the Called Party Numbering Type. You can enter up
to 16 characters, which include digits, the international escape character (+),
asterisk (*), or the pound sign (#). You can enter the word, Default, instead
of entering a prefix.
Tip
|
If the word, Default, displays in the Prefix
field in the Gateway or Trunk Configuration window, you cannot configure the
Strip Digits field in the Gateway or Trunk Configuration window. In this case,
Cisco Unified Communications Manager takes the
configuration for the Prefix and Strip Digits fields from the device pool that
is applied to the device. If the word, Default, displays in the Prefix field in
the Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming called party prefix, which
supports both the prefix and strip digit functionality.
|
Tip
|
To configure the Strip Digits field, you
must leave the Prefix field blank or enter a valid configuration in the Prefix
field. To configure the Strip Digits fields, do not enter the word, Default, in
the Prefix field.
|
- Strip Digits—Enter
the number of digits that you want Cisco Unified Communications Manager to
strip from the called party number of Unknown type before it applies the
prefixes.
- Calling Search
Space—This setting allows you to transform the called party number of Unknown
called party number type on the device. If you choose None, no transformation
occurs for the incoming called party number. Make sure that the calling search
space that you choose contains the called party transformation pattern that you
want to assign to this device.
|
Subscriber Number
|
Configure the following settings to transform incoming called
party numbers that use Subscriber for the Called Party Number Type.
- Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called
numbers that use Subscriber for the Called Party Numbering Type. You can enter
up to 16 characters, which include digits, the international escape character
(+), asterisk (*), or the pound sign (#). You can enter the word, Default,
instead of entering a prefix.
Tip
|
If the word, Default, displays in the Prefix
field in the Gateway or Trunk Configuration window, you cannot configure the
Strip Digits field in the Gateway or Trunk Configuration window. In this case,
Cisco Unified Communications Manager takes the
configuration for the Prefix and Strip Digits fields from the device pool that
is applied to the device. If the word, Default, displays in the Prefix field in
the Device Pool Configuration window,
Cisco Unified Communications Manager applies the
service parameter configuration for the incoming called party prefix, which
supports both the prefix and strip digit functionality.
|
Tip
|
To configure the Strip Digits field, you
must leave the Prefix field blank or enter a valid configuration in the Prefix
field. To configure the Strip Digits fields, do not enter the word, Default, in
the Prefix field.
|
- Strip Digits—Enter
the number of digits that you want Cisco Unified Communications Manager to
strip from the called party number of Subscriber type before it applies the
prefixes.
- Calling Search
Space—This setting allows you to transform the called party number of
Subscriber called party number type on the device. If you choose None, no
transformation occurs for the incoming called party number. Make sure that the
calling search space that you choose contains the called party transformation
pattern that you want to assign to this device.
|
Phone Settings
|
Calling Party Transformation CSS
|
From the drop-down list box, choose the Calling Search Space that contains the Calling Party Transformation Pattern that
you want to apply to devices in this device pool.
When Cisco Unified CM receives a call from a device in this device pool on an inbound line, Cisco Unified CM immediately
applies the calling party transformation patterns in this CSS to the digits in the calling party number before it routes the
call. This setting allows you to apply digit transformations to the calling party number before Cisco Unified CM routes the
call. For example, a transformation pattern can change a phone extension to appear as an E.164 number.
|
Connected Party Settings
|
Connected Party Transformation CSS
|
This setting is applicable for inbound calls
only. This setting allows you to transform the connected party
number on the device to display the connected number in
another format, such as a DID or E164 number. Cisco Unified Communications Manager includes the transformed number in the
headers of various SIP messages, including 200 OK and mid-call
update/reinvite messages for SIP calls and in the Connected Number
Information Element of CONNECT and NOTIFY messages for H.323 and
MGCP calls. Make sure that the Connected Party
Transformation CSS that you choose contains the called party
transformation pattern that you want to assign to this device
pool.
Note
|
If you configure the Connected Party Transformation CSS as
None, the transformation does not match and does not get applied. Ensure that
you configure the Calling Party Transformation pattern used for Connected Party Transformation in a non-null partition
that is not used for routing.
|
|
Redirecting Party Settings
|
Redirecting Party Transformation CSS
|
This setting allows you to transform the redirecting party
number on the device to E164 format.
Cisco Unified Communications Manager includes the
transformed number in the diversion header of invite messages for SIP trunks
and in the Redirecting Number Information Element of setup message (for H.323
and MGCP) sent out of
Cisco Unified Communications Manager. Make sure that
the Redirecting Party Transformation CSS that you choose contains the called
party transformation pattern that you want to assign to this device pool.
Note
|
If you configure the Redirecting Party Transformation CSS as
None, the transformation does not match and does not get applied. Ensure that
you configure the Redirecting Party Transformation CSS in a non-null partition
that is not used for routing.
|
|