FeedbackRegister
Activates notifications on the event or status changes described by the expressions. Notifications are sent in XML format to the
specified URL. Up to 15 expressions may be registered for each of 3 feedback IDs.
ID: <1..3>
The ID of this particular feedback request.
URL(r): <S: 1, 256>
The URL to which notifications are to be sent.
Expression.1..15: <S: 1, 256>
The events or status change to be notified. Valid Expressions are:
Status/Ethernet Status/Calls Event/CallDisconnected
Event/ Status/NTP Status/Registrations
Event/CallFailure Event/Bandwidth Status/LDAP
Status/Zones Event/RegistrationAdded Event/Locate
Status/Feedback Event/CallAttempt Event/RegistrationRemoved
Event/ResourceUsage Status/ExternalManager Event/CallConnected
Event/RegistrationFailure Event/AuthenticationFailure
Example:
xCommand FeedbackRegister ID: 1 URL: "http://192.168.0.1/feedback/" Expression.1:
"Status/Calls" Expression.2: "Event/CallAttempt"
FindRegistration
Returns information about the registration associated with the specified alias. The alias must be registered on the VCS on which the
command is issued.
Alias(r): <S: 1, 60>
The alias that you wish to find out about.
Example:
xCommand FindRegistration Alias: "john.smith@example.com"
Fips
Sets FIPS140-2 cryptographic mode.
Command: <leave/enter/status>
Either enters, leaves or provides the current status of the system's FIPS140-2 cryptographic mode.
Example:
xCommand Fips Command: enter
ForceConfigUpdate
Forces the relevant configuration on this peer to be updated to match that of the cluster master.
This command has no parameters.
Example:
xCommand ForceConfigUpdate
Cisco VCS Administrator Guide (X8.1.1)
Page 476 of 507
Reference material
Command reference — xCommand