WHIP Sender

The WHIP sender component streams media to a remote media server. By default, this will stream to DroneDeploy's media server which can be viewed in the DroneDeploy automate dashboards.

Note

The WHIP sender agent component needs Agent Version 1.7.19+

Configuration

To enable the WHIP sender component, your agent will need a section in its agent-settings.json file for the whip-sender component, as shown below. For more information on how to configure the agent components, see Agent Configuration.

...
"components": [
...
{
  "enabled": true,
  "id": "whip-sender",
  "settings": {
    "logLevel": 4
  }
},
...
]

The WHIP sender component can be extended with the following configuration parameters. Generally, you should not need to modify these settings:

Name	Description	Default	Unit
name	How this instance should be named.	"whip-sender"
logLevel	The logging verbosity: 1 - very quiet, 6 - very talkative.	4
domain	The domain of the WHIP server.	<DroneDeploy API>
streamPath	The path template used to stream media to the domain. When using the default domain, this must not be changed.	/cloudmedia/webrtc/${project}/${callsign}/${topic}/whip

Data Model

The WHIP sender component takes a subscription to a demand topic such as:

/whip-sender/demand?path=/spot/spotcam/streams/video

• The path query parameter selects which media stream the whip-sender should be sending to the WHIP server.

Upon subscription, media is streamed to the WHIP server.

The subscription itself receives diagnostics on the status and throughput of the stream.