There is a certain degree of flexibility in Jingle sessions so that once a session is active, it doesn’t necessarily have to remain fixed in its configuration. Active sessions can be changed to modify or remove content – keeping voice going while stopping video for example – or changing the transport protocol. Jingle can also send information messages between clients.
available under Jingle. Datagram has greece telegram components that exchange packets. These can be of any length and can be received in any order. When using Datagram, the transport has to specify which components are needed and how they will be used.
The alternative is streaming transport; this exchanges bi-directional streams akin to the method seen in TCP. Packets on the stream are received in order and each must have string identifier and a maximum packet length. Which transport should be used is established at the start of the session.
Protecting Jingle
As with any online service, security is an important consideration when using Jingle. Using some form of transport layer security is a good start and as we’ve seen, you can make starting a session conditional on this being present.
Jingle can also be vulnerable to DDoS attacks bombarding clients with too many requests and it’s important to guard against this by configuring the system to only accept connections from known entities. Similarly, you can avoid the interception and redirection of calls by ensuring that session IDs match.
Two different transport types are
-
- Posts: 446
- Joined: Thu Jan 02, 2025 7:18 am