package calling

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc Register (Registration, stream RelayMessage)

  call_sim.proto:79

  The client will register with the server, and this is a "server-side streaming RPC".

• rpc Send (RelayMessage, Empty)

  call_sim.proto:81

  After registering, the client can send messages, and this is a "Simple RPC".

• rpc Ready (Registration, stream CommandMessage)

  call_sim.proto:105

  Each test client will let the server know when it is ready (generally after it registers with the relay server, and thus be able to receive commands).

• rpc Done (Registration, Empty)

  call_sim.proto:107

  The client can let the server (and test manager) know it is done (after stopping).

• rpc Notification (Empty, stream Event)

  call_sim.proto:109

  A simplistic notification scheme to send updates to the test manager.

  message Event

  call_sim.proto:97

  • int32 readyCount = 1

    The number of clients that are ready for the test. Increments with ready, decrements with done.

• rpc SendCommand (CommandMessage, Empty)

  call_sim.proto:111

  The controller can send messages to specific clients in order to instruct them to do things.

Used in: RelayMessage

• optional CallMessage.Offer offer = 1

• optional CallMessage.Answer answer = 2

• repeated CallMessage.IceUpdate iceUpdate = 3

• optional CallMessage.Busy busy = 4

• optional CallMessage.Hangup hangup = 5

Used in: CallMessage

• uint64 id = 1

• bytes opaque = 2

Used in: CallMessage

• uint64 id = 1

Used in: CallMessage

• uint64 id = 1

• Hangup.Type type = 2

• uint32 deviceId = 3

Used in: Hangup

• HANGUP_NORMAL = 0

• HANGUP_ACCEPTED = 1

• HANGUP_DECLINED = 2

• HANGUP_BUSY = 3

• HANGUP_NEED_PERMISSION = 4

Used in: CallMessage

• uint64 id = 1

• bytes opaque = 2

Used in: CallMessage

• uint64 id = 1

• Offer.Type type = 2

• bytes opaque = 3

Used in: Offer

• OFFER_AUDIO_CALL = 0

• OFFER_VIDEO_CALL = 1

Used as request type in: TestManagement.SendCommand

Used as response type in: TestManagement.Ready

• string client = 1

  To, the client that should receive the message.

• CommandMessage.Command command = 2

  The command to send.

Used in: CommandMessage

• START_AS_CALLER = 0

• START_AS_CALLEE = 1

• STOP = 2

Used as request type in: TestManagement.Notification

Used as response type in: SignalingRelay.Send, TestManagement.Done, TestManagement.SendCommand

(message has no fields)

Used as request type in: SignalingRelay.Register, TestManagement.Done, TestManagement.Ready

• string client = 1

  From, the client that is registering.

The RelayMessage is essentially the message envelope, containing the actual call message along with other meta data.

Used as request type in: SignalingRelay.Send

Used as response type in: SignalingRelay.Register

• string client = 1

  From, the client that is sending the message.

• uint32 deviceId = 2

  The deviceId of the client that is sending the message.

• optional CallMessage callMessage = 3

  The actual message we are passing through.

• optional bytes opaqueMessage = 4

  Intended for Group CallMessage, which uses the Opaque field in the Signal Protocol