Release Notes

New features in XC2
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 2 of 21
New features in XC2
New features in XC2.3.1
This is a maintenance release.
New features in XC2.3
New Capacity Management API
A new API allows management applications (such as Cisco TMS) to obtain information about a conference
and its associated resources. The APIreturns information about the capacity of a conference bridge that will
be used for a conference with a given dialed alias.
New Provisioning API
A new APIallows management applications (such as Cisco TMS) to provision conferences on TelePresence
Conductor. The API allows the client to create a new ConfBundle on the TelePresence Conductor.A
ConfBundle consists of information related to a conference and can have a number of aliases and auto-dialed
participants associated with it. These aliases and auto-dialed participants are separate from conference
aliases and auto-dialed participants configured via the TelePresence Conductor’s web interface and can be
edited via the Provisioning API only.
Direct match alias lookup
TelePresence Conductor version XC2.3 supports direct match alias lookup for conferences created via the
Provisioning API. Allowing direct match alias configuration dramatically reduces the lookup time for tens of
thousands of aliases.
In previous versions, conferences configured on TelePresence Conductor used regular expressions (RegEx)
to match aliases. This allowed multiple aliases to create conferences with minimum configuration on
TelePresence Conductor. However, when thousands of aliases were configured, conference lookup time and
create time started to increase, and fine grain control of allowed conferences was difficult.
In version XC2.3 direct match alias lookup is supported only when using the new Provisioning API. All
conferences configured directly via the TelePresence Conductor's web interface or XMLRPCAPI continue
to use RegEx lookup.
Numeric dialing with Unified CM
Unified CMs append the TelePresence Conductor’s IP address (one of the additional IP addresses
configured on TelePresence Conductor's user interface) or hostname instead of the domain to numeric dial
strings. For example, when an endpoint dials the string 1234, Unified CM will send the dial string
1234@10.0.0.1 to TelePresence Conductor. When TelePresence Conductor attempts to do an exact
match of the dial string, it will not be able to match the dial string to an alias, because the user will have
provisioned an alias that uses a domain, for example [e-mail].
A new API (the SIP Domain API) resolves this issue. You can set the SIP domain on TelePresence
Conductor. TelePresence Conductor will transform incoming dial strings to include the SIP domain rather
than an IP address or hostname, which will make it possible to compare the dial string with provisioned
aliases.
Note that this modification to the URI is only internal to the TelePresence Conductor. The outgoing call URI
does not change.