Cisco Cisco TelePresence Management Suite (TMS) Version 15
Setting up and maintaining the Provisioning Directory
Cisco TelePresence Management Suite Agent Legacy Deployment Guide (13.2)
Page 30 of 55
6. Edit the pattern appropriately:
l
We recommend using the default Device URI Pattern {username}.{device.model}
@example.com
@example.com
to easily identify the type of device the user provisions to (that is, ‘movi' or 'e20') and
to maintain unique Device URI Patterns. If more than one user has the same Device URI, this will
create problems with user reporting in Cisco TMS, as the lookup from URI to username can only return
one of the users with this URI.
create problems with user reporting in Cisco TMS, as the lookup from URI to username can only return
one of the users with this URI.
l
Include device.connectivity in the pattern to add the word internal for Cisco VCS Control-
registered users or external for Cisco VCS Express-way registered users to each device URI. A
sample Expressway-registered device URI would look like
this: firstname.lastname.external@example.com.
registered users or external for Cisco VCS Express-way registered users to each device URI. A
sample Expressway-registered device URI would look like
this: firstname.lastname.external@example.com.
l
In addition you can change the words internal and external to for example home and office. The device
URI will then be: firstname.lastname.office@example.com or
firstname.lastname.home@example.com.
URI will then be: firstname.lastname.office@example.com or
firstname.lastname.home@example.com.
l
Note that you cannot replace "internal" or "external" with a blank/space.
Using Regex
Regex is supported in all
Dial Plan Configuration
fields.
Examples
To remove spaces:
{mobilePhone[' '='']}@example.com
To remove spaces and +47:
{mobilePhone[' '='','\+47'='']}@example.com
To extract the domain part of the email address:
{username}.office@{User.emailAddress['^.+?@'='']}
To replace ø with o:
{username['ø'='o']}@example.com
Uploading a new configuration template
Each type of endpoint comes with its own XML template file for provisioning. A new template is usually
provided with each software release, either included in the software deliverable archive, or downloadable
from the same cisco.com page as the product's release notes.
provided with each software release, either included in the software deliverable archive, or downloadable
from the same cisco.com page as the product's release notes.
When you have the required templates available locally:
1. Click Manage Configuration Templates.
2. Click Upload New.
3. Locate and select the configuration template.
4. Click Open.
The new template is now available for configuration.