Title: EyeBeam for Android: A Technical Overview of a Mobile SIP Softphone Author: [Generated for informational purposes] Date: April 14, 2026
Abstract EyeBeam is a legacy Session Initiation Protocol (SIP) softphone developed by CounterPath Corporation, originally designed for desktop operating systems (Windows). While a fully-featured native "EyeBeam for Android" does not exist as a standalone branded product, the technology and protocol implementations that defined EyeBeam have been integrated into CounterPath’s mobile SIP client, Bria . This paper examines the functional equivalent of EyeBeam on the Android platform, detailing its architecture, core VoIP features, security considerations, and practical deployment scenarios. It also addresses the transition from EyeBeam to Bria and the current state of SIP-based softphones on Android.
1. Introduction Voice over IP (VoIP) softphones allow Android devices to place calls over data networks using SIP, a standard signaling protocol. EyeBeam (circa 2005–2010) was one of the most popular desktop SIP clients, known for its wide codec support, presence features, and enterprise interoperability. As mobile usage surpassed desktop, CounterPath shifted focus to Android/iOS clients. While no official "EyeBeam for Android" exists, the Bria Android app inherits EyeBeam's SIP stack, user interface philosophy, and feature set. This paper uses "EyeBeam for Android" to refer to this lineage.
2. Architecture & Protocol Stack The EyeBeam/Bria architecture on Android follows a layered model: | Layer | Components | |-------|-------------| | Hardware Adaptation | Uses Android’s AudioTrack / AudioRecord for audio, native RIL for cellular fallback | | Codec Engine | G.711 (a-law/μ-law), G.722 (wideband), Opus, SILK, iLBC, GSM | | SIP Stack | RFC 3261 compliant, with support for TCP, UDP, TLS | | NAT Traversal | STUN, TURN, ICE (RFC 5245) | | Presence/IM | SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) | | Security | SRTP (RFC 3711), ZRTP, TLS 1.2+ | On Android, the native SIP stack ( android.net.sip ) is limited. EyeBeam's modern counterpart bypasses it entirely, using a custom, cross-platform C++ SIP stack via JNI (Java Native Interface) for low latency and feature parity with desktop. eyebeam for android
3. Key Features of EyeBeam’s Android Equivalent (Bria) CounterPath’s Bria for Android provides:
Multi-account SIP registration – Up to 25 SIP accounts (e.g., office PBX, VoIP provider) Audio codec prioritization – User-configurable codec ordering Presence & BLF – Busy Lamp Field, buddy list with status (Available, Away, DND) Call transfer – Attended and blind transfer Conference calling – 3-way native conferencing Message waiting indicator – Visual notification for voicemail Push notifications – Using Google Firebase Cloud Messaging (GCM/FCM) to save battery (unlike legacy EyeBeam) HD Voice – Wideband audio over Opus/G.722
Missing compared to desktop EyeBeam:
No desktop-style call recording (Android restrictions) No pluggable UI skins Limited diagnostic logging for advanced troubleshooting
4. Implementation Challenges on Android Developing an EyeBeam-like client for Android required solving: | Challenge | Solution | |-----------|----------| | Background VoIP | Android 8+ limits background services → Use FOREGROUND_SERVICE with persistent notification + android.permission.ACCESS_BACKGROUND_LOCATION (for certain NAT keepalives) | | Audio routing | Bluetooth headsets, speakerphone, earpiece – Must implement AudioManager routing logic manually | | Battery drain | Legacy SIP keepalives (every 30 sec) → Replace with FCM push or RFC 8599 Push Notification extensions | | Network switching | WiFi ↔ Cellular handoff → Use ICE restart and ConnectivityManager.NetworkCallback | | Acoustic echo cancellation | Hardware-dependent – Use Android’s AcousticEchoCanceler or software AEC in codec |
5. Security Considerations EyeBeam for Android (Bria) implements: Title: EyeBeam for Android: A Technical Overview of
SRTP for media encryption (AES-128/256) TLS for SIP signaling (prevents eavesdropping on INVITE/REGISTER) Client certificate authentication for enterprise PBX No plaintext credential storage – Uses Android Keystore System VPN compatibility – Works with built-in IKEv2/IPsec VPNs
Limitation: No support for SDES key exchange fallback warning; some deployments still use insecure RTP.