Cisco Cisco MediaSense Release 9.0(1) Developer's Guide
Successful
JSON
Response
Schema:
JSON
Response
Schema:
{
: 2000,
"responseCode"
:
,
"responseMessage"
"Successful"
: {
"responseBody"
:
,
"subscriptionId"
"<This is a
>"
String
: [
,
"subscriptionFilters"
"<This is a
>"
String
"<This is a
,...],
>"
String
:
"tagNameRegEx"
"<java-regular-expression>"
}
}
Failure JSON
Response
Schema:
Response
Schema:
{
: <
is an integer>,
"responseCode"
this
:
,
"responseMessage"
"Failure: <
is a string>"
this
:
"detail"
"<
is a string>"
this
}
Related
Error Codes:
Error Codes:
Go to the
Events
Triggered:
Triggered:
Event Action:
:
Availability
Available since API Version 1.1
Modified in API Version 1.2 (See Notes below.)
Modified in API Version 1.2 (See Notes below.)
Release:
8.5(2)
Notes and
Examples:
Examples:
If the same subscriptionUri is subscribed for a second time, the subscriptionFilters in the existing subscription will
be replaced with the new subscriptionFilters. If the subscriptionFilters are also the same, then no error is
generated. A 2005 responseCode is generated indicating that the subscription already exists.
The following changes were introduced in Release 8.5(3), Version 1.2: Parameters introduced:
be replaced with the new subscriptionFilters. If the subscriptionFilters are also the same, then no error is
generated. A 2005 responseCode is generated indicating that the subscription already exists.
The following changes were introduced in Release 8.5(3), Version 1.2: Parameters introduced:
tagNameRegEx
Examples for subscribeToEvents
Example 1
To receive event notifications for all events:
HTTP POST:
https://10.194.118.1:8440/ora/eventService/event/subscribeToEvents
Headers:
Content-Type: application/json
JSESSIONID: <the jsessionId received from a signIn request>
46