{
  "id": 6777163,
  "title": "VoIP, VPN, and the Build System Behind Them",
  "url": "https://urgent.news/2026/09/11/voip-vpn-and-the-build-system-behind-them",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-11T17:01:39.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/codenameone/voip-vpn-and-the-build-system-behind-them-58j3"
  },
  "original_language": "en",
  "account": null,
  "summary": "Codename One, an open-source framework for building native apps from a single Java or Kotlin codebase, has introduced significant enhancements to its VoIP and VPN capabilities. In 2019, the framework's ability to include VoIP and VPN features was limited due to the complexity of integrating native APIs across different platforms. However, the introduction of a builder system has enabled Codename One to handle these integrations more efficiently. The builder system allows for the assembly of native products, linking frameworks, injecting permissions, and generating native delegates and services based on the actual Java packages used in the application. This approach ensures that only the necessary native components are included in the final product, reducing complexity and maintenance overhead. PR #5604 introduced first-class call management, VoIP push handling, managed VPN, and the packet-tunnel API on Android, while PR #5693 completed the iOS path by generating a separately translated and signed Network Extension. The Java API now provides a unified interface for developers to implement these features, while the builder system manages the complex native integration behind the scenes. With these updates, developers can now seamlessly connect application call state to CallKit on iOS and self-managed ConnectionService on Android, while maintaining control over their media and signaling stack. Additionally, managed VPN capabilities have been expanded to support both managed IPsec and IKEv2 profiles on both iOS and Android platforms, providing developers with greater flexibility in implementing secure connections.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}