Phone call, see here » for more info on the full flow.
phoneCall#30535af5 flags:# p2p_allowed:flags.5?true video:flags.6?true conference_supported:flags.8?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int custom_parameters:flags.7?DataJSON = PhoneCall;
| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| p2p_allowed | flags.5?true | Whether P2P connection to the other peer is allowed |
| video | flags.6?true | Whether this is a video call |
| conference_supported | flags.8?true | If set, the other party supports migrating the call to a conference call »; clients should only offer the migrate/"Add participants" option in the call UI when this flag is set. |
| id | long | Call ID |
| access_hash | long | Access hash |
| date | int | Date of creation of the call |
| admin_id | long | User ID of the creator of the call |
| participant_id | long | User ID of the other participant in the call |
| g_a_or_b | bytes | Parameter for key exchange |
| key_fingerprint | long | Key fingerprint |
| protocol | PhoneCallProtocol | Call protocol info to be passed to libtgvoip |
| connections | Vector<PhoneConnection> | List of endpoints the user can connect to exchange call data |
| start_date | int | When was the call actually started |
| custom_parameters | flags.7?DataJSON | Custom JSON-encoded call parameters to be passed to tgcalls. |
Telegram supports end-to-end-encrypted one-to-one voice and video calls.
Deprecated description of encryption in voice calls as implemented in Telegram apps older than version 7.0.