Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
3.
We recommend that you set Caller ID to
FindMe ID. The options are:
—
FindMe ID: the caller ID of a call being made through this Cisco VCS is replaced with the relevant FindMe ID.
—
Incoming ID: the caller ID is not altered; the caller ID presented to the called endpoint will be the ID of the
endpoint initiating the call.
endpoint initiating the call.
.
4.
Click Save.
Sending and Returning Calls via ISDN Gateways
This section describes how to use FindMe with calls that are routed via an ISDN gateway (for example, when calling a
mobile phone, or some other ISDN accessible destination).
mobile phone, or some other ISDN accessible destination).
If the Cisco VCS has Caller ID (Applications > FindMe) set to use the
FindMe ID, the caller ID presented will be the
user's E.164 phone number. The E.164 phone number would either have been entered manually when the user account
was configured, or supplied by AD (from the Office Phone number) if Cisco TMS created the account for AD provisioned
users.
was configured, or supplied by AD (from the Office Phone number) if Cisco TMS created the account for AD provisioned
users.
If the called party returns the call (and the E.164 Alias is routed by the network to an ISDN gateway on the video
network), the call will be received by the ISDN gateway and forwarded to Cisco VCS with the E.164 phone number as
the called number.
network), the call will be received by the ISDN gateway and forwarded to Cisco VCS with the E.164 phone number as
the called number.
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.
70
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide