@bmalkow If possible, please review my source code which is for now stored in voip branch of Halcyon repository. There is a code to parse SDP by building data blocks, then generating SDP from those blocks. As well there is a code to parse <content/> and other subelements of <jingle/> into data blocks and to serialize those data blocks in to the <content/> element.

If you would be looking at it, please let me know if everything it OK with Kotlin conventions or something should be done differently.

@bmalkow I've moved all of the code responsible for handling VoIP (Jingle) from TigaseSwift to Halcyon.

There is still code missing related to handling of Jingle session and actual WebRTC integration, but in case of iOS apps, this code is part of the app as it relies on the VoIP implementation and API (WebRTC libraries, iOS notifications/macOS windows, etc).

Should we have a basic (multi account) manager class for handling Jingle sessions in Halcyon or actual reaction on the event should be part of the app? (I would say, that this is an app responsibility to act on the event).

Implementation is mostly ready but not tested.