-
Notifications
You must be signed in to change notification settings - Fork 632
WebRTC WebSocket Messaging Reference
Ahmet Oğuz Mermerkaya edited this page Aug 15, 2020
·
26 revisions
This documentation is for developers who needs to implement signalling between Ant Media Server and clients for publishing & playing streams. Let's make it step by step
- Client connects to Ant Media Server through WebSocket. URL of the WebSocket interface is something like
ws://SERVER_NAME:5080/WebRTCAppEE/websocket
- Client sends publish JSON command to the server with stream name parameter. (Remove token parameter if token control is not enabled)
{
command : "publish",
streamId : "stream1",
token : "tokenId",
}
- If Server accepts the stream, it replies back with start command
{
command : "start",
streamId : "stream1",
}
- Client inits peer connections, creates offer sdp and send the sdp configuration to the server with takeConfiguration command
{
command : "takeConfiguration",
streamId : "stream1",
type : "offer",
sdp : "${SDP_PARAMETER}"
}
- Server creates answer sdp and send the sdp configuration to the client with takeConfiguration command
{
command : "takeConfiguration",
streamId : "stream1",
type : "answer",
sdp : "${SDP_PARAMETER}"
}
- Client and Server get ice candidates several times and sends to each other with takeCandidate command
{
command : "takeCandidate",
streamId : "stream1",
label : "${CANDIDATE.SDP_MLINE_INDEX}",
id : "${CANDIDATE.SDP_MID}",
candidate : "${CANDIDATE.CANDIDATE}"
}
- Clients sends stop JSON command to stop publishing
{
command : "stop",
streamId: "stream1"
}
- Client connects to Ant Media Server through WebSocket.
ws://SERVER_NAME:5080/WebRTCAppEE/websocket
- Client sends play JSON command to the server with stream name parameter. (Remove token parameter if token control is not enabled)
{
command : "play",
streamId : "stream1",
token : "tokenId",
}
- If Server accepts the stream, it replies back with offer command
{
command : "takeConfiguration",
streamId : "stream1",
type : "offer",
sdp : "${SDP_PARAMETER}"
}
- Client creates answer sdp and send the sdp configuration to the server with takeConfiguration command
{
command : "takeConfiguration",
streamId : "stream1",
type : "answer",
sdp : "${SDP_PARAMETER}"
}
- Client and Server get ice candidates several times and sends to each other with takeCandidate command
{
command : "takeCandidate",
streamId : "stream1",
label : "${CANDIDATE.SDP_MLINE_INDEX}",
id : "${CANDIDATE.SDP_MID}",
candidate : "${CANDIDATE.CANDIDATE}"
}
- Clients sends stop JSON command to stop playing
{
command : "stop",
streamId: "stream1",
}
- Peers connects to Ant Media Server through WebSocket.
ws://SERVER_NAME:5080/WebRTCAppEE/websocket
- Client sends join JSON command to the server with stream name parameter.
{
command : "join",
streamId : "stream1",
}
If there is only one peer in the stream1, server waits for the other peer to join the room.
- When second peer joins the stream, server sends start JSON command to the first peer
{
command : "start",
streamId : "stream1",
}
- First peer create offer sdp and send to the server with takeConfiguration command,
{
command : "takeConfiguration",
streamId : "stream1",
type : "offer",
sdp : "${SDP_PARAMETER}"
}
Server relays the offer sdp to the second peer
- Second peer creates answer sdp and sends to the server with takeConfiguration command
{
command : "takeConfiguration",
streamId : "stream1",
type : "answer",
sdp : "${SDP_PARAMETER}"
}
Server relays the answer sdp to the first peer
- Each peers get ice candidates several times and sends to each other with takeCandidate command through server
{
command : "takeCandidate",
streamId : "stream1",
label : "${CANDIDATE.SDP_MLINE_INDEX}",
id : "${CANDIDATE.SDP_MID}",
candidate : "${CANDIDATE.CANDIDATE}"
}
- Clients sends leave JSON command to leave the room
{
command : "leave",
streamId: "stream1"
}
- Peers connects to Ant Media Server through WebSocket.
ws://SERVER_NAME:5080/WebRTCAppEE/websocket
- Client sends join JSON command to the server with room name parameter.
streamId
field is optional in casestreamId
should be specified in advance. IfstreamId
is not sent, server returns with a randomstreamId
in the second message.
{
command : "joinRoom",
room : "room_id_for_your_conference",
streamId: "stream_id_you_want_to_use"
}
- Server notifies the client with available streams in the room
{
command : "notification",
definition : "joinedTheRoom",
streamId: "unique_stream_id_returned_by_the_server"
streams: [
"stream1_in_the_room",
"stream2_in_the_room",
...
]
}
streamId
returned by the server is the stream id client uses to publish stream to the room.
streams
is the json array which client can play via WebRTC. Client can play each stream by play method above. This streams array can be empty if there is no stream in the room.
- Web app should pull the server periodically for the room info as follows,
{
command : "getRoomInfo",
room : "room_id_for_your_conference",
streamId: "unique_stream_id_returned_by_the_server"
}
- Server returns the active streams in the room as follows. Application should synchronize the players in their side.
{
command:"roomInformation",
room: "room_id_for_your_conference",
streams: [
"stream1_in_the_room",
"stream2_in_the_room",
...
]
}
- Any user can leave the room by sending below message
{
command : "leaveFromRoom",
room: "roomName"
}
-
noStreamNameSpecified
: it is sent when stream id is not specified in the message.
{
command : "error",
definition : "noStreamNameSpecified",
}
-
not_allowed_unregistered_streams
: This is sent back to the user if the publisher wants to send a stream with an unregistered id and server is configured not to allow this kind of streams
{
command : "error",
definition: "not_allowed_unregistered_streams",
}
-
no_room_specified
: This is sent back to the user when there is no room specified in joining the video conference.
{
command : "error",
definition : "no_room_specified",
}
-
unauthorized_access
:This is sent back to the user when the token is not validated
{
command : "error",
definition : "unauthorized_access",
}
-
no_encoder_settings
:This is sent back to the user when there are no encoder settings available in publishing the stream.
{
command : "error",
definition : "no_encoder_settings",
}
-
no_peer_associated_before
: This is peer to peer connection error definition.It is sent back to the user when there is no peer associated with the stream.
{
command : "error",
definition : "no_peer_associated_before",
}
-
notSetLocalDescription
: It is send when local description is not set successfully
{
command : "error",
definition : "notSetLocalDescription",
}
Whenever you send a ping command to the server, it will respond you with pong command. Ping Command
{
command : "ping",
}
Pong Response from Server
{
command : "pong",
}
- Introduction
- Quick Start
- Installation
- Publishing Live Streams
- Playing Live Streams
- Conference Call
- Peer to Peer Call
- Adaptive Bitrate(Multi-Bitrate) Streaming
- Data Channel
- Video on Demand Streaming
- Simulcasting to Social Media Channels
- Clustering & Scaling
- Monitor Ant Media Servers with Apache Kafka and Grafana
- WebRTC SDKs
- Security
- Integration with your Project
- Advanced
- WebRTC Load Testing
- TURN Servers
- AWS Wavelength Deployment
- Multi-Tenancy Support
- Monitor Ant Media Server with Datadog
- Clustering in Alibaba
- Playlist
- Kubernetes
- Time based One Time Password
- Kubernetes Autoscaling
- Kubernetes Ingress
- How to Install Ant Media Server on EKS
- Release Tests
- Spaceport Volumetric Video
- WebRTC Viewers Info
- Webhook Authentication for Publishing Streams
- Recording Streams
- How to Update Ant Media Server with Cloudformation
- How to Install Ant Media Server on GKE
- Ant Media Server on Docker Swarm
- Developer Quick Start
- Recording HLS, MP4 and how to recover
- Re-streaming update
- Git Branching
- UML Diagrams