Specifications

D-6
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Appendix D Creating and Manipulating Session Shifting Files
Profile Manager
For example, for the delivery service with a Service Routing Domain Name of sr.cds.com, the following
link can be used to address the Profile Manager to provision profiles:
http://sr.cds.com/api/services/profile_mgr
Profile Lists
Profile Lists in XML format are used to add, append, and delete profile entries through the Profile
Manager. The following is an example of a Profile List for a delivery service:
<?xml version="1.0"?>
<ws:ProfileList
xmlns="http://www.cisco.com/schemas/VCNBU/SCTE130Impl/2007/R1/ciscowebsvc"
xmlns:ws="http://www.cisco.com/schemas/VCNBU/SCTE130Impl/2007/R1/ciscowebsvc"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=
"http://www.cisco.com/schemas/VCNBU/SCTE130Impl/2007/R1/ciscowebsvc ciscowebsvc.xsd''>
<Profile id="1">
<UserAgent>QuickTime</UserAgent>
<CapabilitiesUrl>http://apple.com/capabilities/quicktime</CapabilitiesUrl>
</Profile>
<Profile id="2">
<UserAgent>WMPlayer</UserAgent>
<CapabilitiesUrl>http://microsoft.com/capabilities/wmplayer</CapabilitiesUrl>
</Profile>
</ws:ProfileList
This Profile List has two profiles defined. The first one will be used for QuickTime clients that identify
themselves as a QuickTime user agent or provide the capability URL shown. The second one will be used
for Windows Media Player clients that identify themselves as a Windows Media Player user agent or
provide the capabilities URL shown.
Note The user agent and capabilities URL depend on the URL provided by the client in the RTSP messages.
Also note that the example above creates a single profile for all QuickTime clients, regardless of their
supported bandwidth or other specifications. If it is required to have profiles defined with finer
granularities, this can be done as long as the profiles have different user agents and capabilities URLs.
Profiles in Content Lists
When provisioning content entries using Content Lists, a profile ID can be specified for each content
entry within a content set. This is done by including a Profile tag in the Ext element of the particular
content entry. If no profile ID is specified for a particular entry, a default of Profile id= “0” is given. The
following content set has been modified to include profile IDs:
<core:Content>
<core:URI>rtsp://cds.com/pirates.mov</core:URI>
<core:Ext>
<Profile id=”1”>
<core:Content>
<core:URI>rtsp://cds.com/pirates.pc.mov</core:URI>