In brief: Yeastar Linkus is the desktop and mobile client for Yeastar P-Series PBX systems, and getting it right is essential for SA resellers deploying Yeastar for clients. This guide covers Linkus features, configuration, known issues, and deployment best practices.
What Is Yeastar Linkus?
Linkus is Yeastar’s unified communications client — available as a Windows/Mac desktop application, a web browser client, and iOS/Android mobile apps. Together, these clients allow Yeastar P-Series users to make and receive calls, send messages, join meetings, manage presence, and access the company directory from any device, anywhere.
For SA businesses deploying Yeastar P-Series (either self-hosted or through Yeastar Cloud), Linkus is typically the primary user interface — most users interact with the PBX through Linkus rather than through desk phones alone. Getting Linkus configured correctly and ensuring users know how to use it is therefore central to a successful deployment.
Linkus Client Features
Desktop App (Windows/Mac):
- Full softphone functionality — make, receive, transfer, and conference calls
- Internal messaging and group chat
- Presence and availability status (Available, Busy, DND, Away, On Call)
- Company directory with search and click-to-call
- Call history and voicemail access
- Integration with Microsoft Outlook and other contact sources
- Screen share for Yeastar meetings
Web Client:
The Linkus Web Client works in modern browsers without any software installation. This makes it practical for remote workers who don’t have admin rights to install desktop software, or for hot-desking environments where users need access from any workstation. Features are comparable to the desktop app with the exception of some advanced audio configuration options.
Mobile Apps (iOS/Android):
- Receive and make calls using the business extension number
- Push notification support for incoming calls on iOS (uses APNs) and Android (uses FCM)
- Messaging and presence
- Voicemail with transcription (where configured)
Linkus Deployment: Step-by-Step Configuration
Enable Linkus in P-Series admin console:
Navigate to Apps → Linkus → General. Ensure Linkus is enabled and the relevant licence is active. Yeastar P-Series licences include a specific Linkus user count — verify the licence covers all intended users.
Configure Linkus server settings:
Linkus requires the P-Series to be reachable from both the internal network and external internet (for mobile app users and remote workers). Set the P-Series’s external hostname/IP correctly in System → Network → General. If the server is behind NAT, configure port forwarding for the Linkus required ports.
Provision user accounts:
Each extension user needs a Linkus account. In Yeastar P-Series, navigate to Admin → User Management and ensure each user has an email address configured — this is used for Linkus login and QR code provisioning. Use the bulk provisioning QR code feature to send each user a setup email with their personalised QR code, which the mobile app scans to configure automatically.
Test all clients:
After provisioning, test: desktop app login and call, web client login and call, mobile app iOS/Android registration and background call reception. Identifying issues before go-live saves support calls post-deployment.
Common Linkus Issues in SA Deployments
Mobile app not ringing when phone is locked: This is the same iOS background limitation discussed in other VoIP mobile app contexts. For Linkus on iOS, verify APNs push is working (check P-Series logs under Apps → Linkus → Logs) and that iOS notifications are enabled for the Linkus app. On Android, disable battery optimisation for Linkus in device settings.
Audio echo on desktop calls: Usually caused by a microphone/speaker configuration issue on the workstation. In Linkus Desktop settings, select the correct audio input device (headset microphone, not internal speakers) and confirm the echo cancellation setting is enabled. Using a USB headset rather than built-in laptop speakers and microphone significantly reduces echo.
Linkus Web Client call quality issues: Browser-based VoIP depends on WebRTC, which requires a stable connection with low jitter. If web client users report audio issues during peak internet usage hours, the problem may be ISP contention rather than Linkus configuration. QoS on the office router for VoIP traffic addresses this.
External users can’t connect: If Linkus works inside the office but not externally, this is typically a network/firewall issue. Verify port forwarding is configured for the P-Series external hostname and that the relevant ports (HTTPS for Linkus, the RTP ports for call media) are open on the firewall and router.
Linkus vs 3CX Client: Reseller Perspective
Resellers who work with both 3CX and Yeastar P-Series will be asked by clients to compare the softphone clients. Both Linkus and the 3CX app are capable, polished products — the differences are relatively minor:
Linkus has a slightly more modern interface design and the web client is particularly strong. 3CX’s Windows app integrates more deeply with Windows contacts and Microsoft Office. Both have comparable iOS/Android apps with similar push notification behaviour. For most SA deployments, user preference comes down to familiarity rather than any significant functional advantage on either side.
What This Means for SA Telecoms Resellers
Linkus is the face of the Yeastar platform for most end users — they may never see the P-Series admin console, but they use Linkus every day. Investing time in understanding Linkus deeply, training end users properly at go-live, and providing clear documentation for common tasks (how to transfer a call, how to set up voicemail, how to use the mobile app) translates directly into lower support burden and higher client satisfaction.
Consider creating Linkus quick-start guides specific to the roles in each client organisation — a receptionist guide focused on transferring calls and managing the company directory; an executive guide focused on the mobile app and presence management; a helpdesk agent guide focused on call queues and wrap-up codes. Tailored documentation is more useful than generic manuals and takes relatively little time to produce once you have a template.
About the Author
Mechelle Gindra
Mechelle Gindra is the managing editor and lead content strategist at Telecoms-Channel, South Africa's dedicated intelligence platform for telecoms resellers, ICT distributors, and channel partners. She oversees the editorial team's AI-assisted content production pipeline, ensuring vendor news, market analysis, and regulatory updates are accurate, timely, and actionable for the SA telecoms channel community. With deep expertise in the South African telecoms reseller ecosystem, Mechelle directs coverage of vendor partner programmes, ICASA regulatory developments, wholesale market dynamics, and channel business strategy. She is responsible for maintaining Telecoms-Channel's editorial standards, fact-checking processes, and corrections policy.
