Add type for Hangup messages, to reflect either normal hangup or hangup
because the call was accepted elsewhere.
Add type to Offer messages, which is used to indicate the type of call
that is being originated, either an audio call (the same as all legacy
calls) or a video call.
Add level for all messages, which is used to filter feature support,
either legacy or multi-ring behavior.
If the feature level for the Call Message is detected as legacy, AND if
the device is NOT the primary, drop the incoming Call Message.
Always mark outgoing Call Messages as multi-ring capable.
Adjust RingRTC interfaces to support:
- Call Media Type (default is always audioCall for now)
- The Hangup Type, which can be either normal (i.e. regular hangup) or
accepted, replacing the removed Accepted message.
Hangups can now be sent out as a legacy messages or new messages. The
format is the same so that legacy clients will ignore 'new' hangups
sent to squelch ringing if they were actually the 'winner'.
Passing information for receivedOffer and receivedAnswer APIs to
indicate if the sender is a legacy sender or not. Legacy here means
someone using the protocol before the FeatureLevel was added to the
prototol for Call Messages.
Passing information to receivedOffer to indicate if the local device
is primary or not. As a result, if the device is receiving the offer
from a legacy device and is non-primary, the offer shall be ignored.
In this case, a new event is fired:
endedIgnoreCallsFromNonMultiringCallers
Co-authored-by: Michael Kirk <michael@signal.org>
