package signaling

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Answer

signaling.proto:21

A serialized one these goes in the "opaque" field of the CallingMessage::Offer in SignalService.proto

message CallMessage

signaling.proto:76

A generic calling message that is opaque to the application but interpreted by RingRTC. A serialized one of these goes into the "Opaque" field in the CallingMessage variant in Signal protocol messages.

message CallMessage.RingIntention

signaling.proto:77

Used in: CallMessage

enum CallMessage.RingIntention.Type

signaling.proto:78

Used in: RingIntention

message CallMessage.RingResponse

signaling.proto:89

Used in: CallMessage

enum CallMessage.RingResponse.Type

signaling.proto:90

Used in: RingResponse

message ConnectionParametersV4

signaling.proto:62

Used in: Answer, Offer

message IceCandidate

signaling.proto:30

A serialized one these goes in the "opaque" field of the CallingMessage::Ice in SignalService.proto Unlike other message types, the ICE message contains many of these, not just one. We should perhaps rename this to "IceUpdate" since it can either be a candidate or a removal of a candidate. But it would require a lot of FFI code to be renamed which doesn't seem worth it at the moment.

message IceCandidateV3

signaling.proto:40

Used in: IceCandidate

message Offer

signaling.proto:16

A serialized one these goes in the "opaque" field of the CallingMessage::Offer in SignalService.proto For future compatibility, we can add new slots (v5, v6, ...)

message SocketAddr

signaling.proto:44

Used in: IceCandidate

message VideoCodec

signaling.proto:57

Used in: ConnectionParametersV4

enum VideoCodecType

signaling.proto:49

Used in: VideoCodec