uspControllerPath

Value Type

word

Default Value

/controller-path

Description

This parameter specifies the MTP-specific resource used by the USP Controller to receive USP records. The value of this testvar should be derived from the value of the uspControllerMTP testvar as follows:

• If MTP is websocket, uspControllerPath should be set to the value of the “path-abempty” component in the http/https URI or the “path” component in the ws/wss URI used by the USP Controller to receive USP records. For example, if the USP Controller’s http URI is http://6.0.0.2:80/path/to/controller, then uspControllerPath should be set to /path/to/controller. See [RFC 7230] Sections 2.7.1 and 2.7.2 for details on the “path-abempty” component of http/https URI’s and [RFC 6455] Section 3 for details on the “path” component of ws/wss URI’s.

• If MTP is stomp, uspControllerPath should be the value of the “destination” header in SUBSCRIBE messages sent by the USP Controller in order to receive USP records. For example, if the STOMP destination used by the USP Controller is /path/to/controller, then uspControllerPath should be set to /path/to/controller. See the STOMP Protocol Specification, version 1.2 for details on STOMP subscriptions and destinations.

• If MTP is mqtt, uspControllerPath should be the topic name of the topic that the USP Controller subscribes to. For example if the USP Agent publishes messages to the topic /my/controller the value of the uspControllerPath testvar should be /my/controller. See MQTT, version 5.0 for details on subscriptions and topic names.

This testvar was added in CDRouter 11.0