Cisco Cisco MediaSense Release 9.0(1) 开发者指南

下载
页码 136
trackStartDate
Output integer. The number of milliseconds since Jan 1, 1970 GMT when the
track recording started (when the Call Control Service received the 200 OK
message from Unified CM or CUBE). Cisco MediaSense sends an
acknowledgment (ACK) back to Unified CM or CUBE accordingly. 
API Parameter Description u to z
Go to: 
Parameter
Which APIs/Events?
Description and Constraints
urls
Output. JSON Object.  Includes information on the httpUrl and the rtspUrl parameters.
username
Required input string. The Unified CM user who is provisioned as a Cisco MediaSense
user. Unified CM uses "User ID" while Cisco MediaSense uses 
. Not
username
case-sensitive. All Unified CM User ID restrictions apply. Because CUBE uses SSH
authentication, Cisco MediaSense Release 9.0(1) uses Unified CM authentication for all
Cisco MediaSense users. 
xRefCi
All APIs/Events in the list are output strings; 
 is both an output string
and an optional input string. The Unified CM identifier for a particular media stream.
These APIs/Events do not always correspond one-to-one with the recorded tracks.
However, you must use this identifier to correlate the Unified CM JTAPI events to
recorded sessions. 
xRefCi is present when the callControllerType for a session = "Cisco-SIPGateway" or
"Cisco-CUCM".  xRefCi is omitted when callControllerType = "direct". CUBE does not use
this identified. Instead, Cisco MediaSense generates the xRefCi where required. 
Job States
Job States
 
Job States
 
Description
 
39