Cisco Cisco TelePresence Management Suite (TMS) Version 15
Cisco VCS therefore needs to be configured to route this call to the relevant FindMe ID in order to call the user's
endpoints. This can be carried out either by using another FindMe entry, or by setting up ENUM.
endpoints. This can be carried out either by using another FindMe entry, or by setting up ENUM.
Using FindMe to Convert E.164 Alias’s to FindMe IDs
This method uses an additional FindMe account to redirect E.164 dialed numbers to URIs.
For each user with both a URI-style or H.323 ID FindMe ID and an associated E.164 phone number, set up a second
user account with:
user account with:
■
the Username, for example
123456-name.surname
■
the FindMe ID set to the user's E.164 phone number
■
the Principal device address set to the FindMe ID of their main account
This is a static mapping, so the user will not ever need to log in to this second (E.164) account. Any changes to devices
associated with that user are always made in their main account.
associated with that user are always made in their main account.
Using ENUM to Convert E.164 Alias’s to FindMe IDs
Using ENUM allows incoming E.164 Alias's to be looked up in an ENUM server and the call forwarded to the URI
associated with that number.
associated with that number.
To use ENUM conversion, for each FindMe account you must set up the phone number as the ENUM address in the
DNS server and then map that address to the FindMe ID for that account.
DNS server and then map that address to the FindMe ID for that account.
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.
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.
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.
72
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide