N/A
N/A
10.1.182.0
<tr369_websocket_uri idx="INDEX" perm="PERMISSIONFLAG">VALIDVALUE</tr369_websocket_uri>
It sets the WebSocket URI to reach the corresponding USP Controller. This setting is used to filled the content of the Device.LocalAgent.Controller.{i}.MTP.1.WebSocket.
parameter table properly.
For security purpose, the listening socket related to the |
The syntax is the following: <scheme>://<host>:<port>/<path>
Syntax elements | Valid values | Description | Reference links |
---|---|---|---|
(optional) |
| Related to When not provided, but the port is 443, encryption is enabled. Otherwise, it is disabled. | |
(mandatory) |
| Related to IP address or FQDN to be resolved by the USP Agent | |
(optional) |
| Related to Must be set to the listening port configured on the server. When not provided, but the scheme is, the default port of the given scheme is used (e.g. 80 for "ws" and 443 for "wss"). Otherwise, it is 80. | |
(optional) |
| Related to The path in order to exchange USP messages with the WebSocket server. The |
While the <host>
element is mandatory, the others are optional and will be substituted accordingly to RFC 6455 Section 3 (WebSocket URIs).
This setting ignores the query component (starting with " |
Note: the index=1 is reserved for SRAPS while index=2 is available to a custom controller.
Refer to TR-369 - Full Endpoint Management for more details.
Any URI valid according to both RFC 6455 Section 3 (WebSocket URIs) and RFC 3986 Section 3 (URI Generic Syntax).
Examples:
ws://10.0.0.8:8088/usp/endpoints
wss://10.0.0.8:8443/phones/{mac}
wss://dm.mydomain.example/
empty