Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Full configuration and implementation details for ENUM are described in
ENUM dialing on Cisco VCS Deployment
Guide.
Including the ISDN Gateway Prefix in the Caller ID
It is easier to return a PSTN / ISDN call that has been received through an ISDN gateway if the Cisco VCS is configured
to include the prefix of the ISDN gateway in the caller ID.
to include the prefix of the ISDN gateway in the caller ID.
To configure the Gateway caller ID on the Cisco VCS:
1.
Go to Configuration > Protocols > H.323.
2.
Set the Gateway Caller ID as appropriate. The options are:
—
Include prefix: the caller ID displayed on the receiving phone is the caller's phone number prefixed by the
ISDN gateway's prefix. This means the recipient can directly return the call by selecting the number and
pressing return call (provided that an appropriate search rule is in place to allow calls with this prefix to be
routed to the ISDN gateway). This is the recommended option.
ISDN gateway's prefix. This means the recipient can directly return the call by selecting the number and
pressing return call (provided that an appropriate search rule is in place to allow calls with this prefix to be
routed to the ISDN gateway). This is the recommended option.
—
Exclude prefix: the caller ID displayed on the receiving phone is just the caller's phone number. To return the
call, the number must either be redialed or edited prefixing it with the gateway prefix so that the call can be
routed via the gateway to the telephone network.
call, the number must either be redialed or edited prefixing it with the gateway prefix so that the call can be
routed via the gateway to the telephone network.
Note that if the Cisco VCS interworks an E164 H.323 call, it creates a caller ID with a domain set to the IP address of the
VCS that carried out the interworking. Appropriate search rules must be created to handle the routing of these calls, or a
transform implemented that converts
VCS that carried out the interworking. Appropriate search rules must be created to handle the routing of these calls, or a
transform implemented that converts
number@IPofVCS
into
number@LocalSipDomain
.
Regenerating FindMe Locations and Devices
When you create or update location and device templates, the changes are not propagated out to impacted FindMe
accounts until you issue the command to do so by clicking Regenerate Locations and Devices....
accounts until you issue the command to do so by clicking Regenerate Locations and Devices....
You can issue this command at a number of levels, as explained below.
Level
Description
Account
Locations and devices are regenerated only for the selected account, based on the
templates available to that account.
templates available to that account.
This option is useful, for example, to test the impact of changes you have made to
FindMe location and device templates before regenerating at group level.
FindMe location and device templates before regenerating at group level.
Group
Locations and devices are regenerated recursively for all accounts in the selected group
and subgroups.
and subgroups.
This option is useful if, for example, the changes you make to location and device
templates have an impact only on a few particular groups.
templates have an impact only on a few particular groups.
Location template
Locations and devices are regenerated recursively for all groups to which the location
template is assigned. All device templates associated with the location template are also
applied during regeneration.
template is assigned. All device templates associated with the location template are also
applied during regeneration.
This option is useful if, for example, you make changes to a location template that is
associated to a number of groups.
associated to a number of groups.
Device template
Devices are regenerated recursively for all impacted groups. Changes are only taken
into account on existing device templates. New device templates are
into account on existing device templates. New device templates are
not taken into
account.
This option is useful if, for example, you make changes to a particular device template
that is linked to a number of location templates and impacts a number of groups.
that is linked to a number of location templates and impacts a number of groups.
71
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide