Never Works
Response from developer
Thank you for reporting these issues. Based on the documented updates and known fixes, here is how each of your concerns can be addressed: 1. Calls Hang Up Immediately After Answering (on Linkus iOS) This is often caused by MTU size issues in the SIP INVITE or 200 OK packets, especially when using UDP over certain networks (common in remote scenarios). Root Cause: SIP packets exceeding the standard MTU (1500 bytes) may be dropped by network devices, preventing proper call setup even though the push notification arrives. Solution: Enable TLS or TCP transport for the affected extension: Go to PBX Settings > SIP Settings > Transport and ensure TLS is enabled (requires PBX reboot). Edit the extension: Extension and Trunk > Extension > [Your Extension] > SIP Settings. Set Transport to TLS or TCP. On the Linkus iOS app, log out and log back in so it re-registers using the new transport. This forces SIP signaling to use a reliable transport that handles large packets correctly. Note: This fix is confirmed effective in cases where "Linkus audio connecting" appears but the call fails—matching your symptom of answering then immediate hang-up. 2. Call Forwarding / Roll-Over Doesn’t Work When Out of Office This typically relates to Presence-based call forwarding rules not triggering as expected. Ensure your extension’s Presence settings are configured correctly: Go to Extension and Trunk > Extension > [Your Extension] > Presence. Under Call Forwarding, verify the “When Unavailable” or “When Offline” rule points to the correct destination (e.g., voicemail, another extension, or queue). If using Hot Desking, confirm you’re properly logged in/out on your office phone when away. Also check that Linkus is set to accept calls in your current presence state (e.g., if “Off Work” is active, ensure Linkus isn’t excluded from ringing). ⚠️ Avoid circular forwarding (e.g., a ring group member forwarding back to the same ring group), which can cause calls to drop instead of rolling over. 3. Office Phones Display Wrong Time Daily This issue has been fixed in recent firmware: In firmware version 37.23.0.23 / 83.23.0.23 (V24.1-Beta), a known bug was resolved where Wallboard and phones displayed time one hour ahead of the PBX system time. Action Required: Upgrade your PBX to version 37.23.0.23 (Appliance), 83.23.0.23 (Software), or later. After upgrade, confirm PBX Settings > System > Time Zone is correctly set. Reboot IP phones or force a reprovision to sync the corrected time. If the problem still remains unsolved, please send us a detailed description of your problem for our technical support team (helpdesk@yeastar.com) to review. Thank you for your support and understanding.
Not ideal
Clients, which is not ideal on client service.
Response from developer
If your Linkus Mobile app is not receiving push notifications for incoming calls. This can happen if: The app was force-closed (killed) before or during a PBX firmware upgrade. Push notifications are disabled either on the PBX extension settings or within the Linkus app itself. The device lacks network connectivity (Wi-Fi or cellular data) when the call arrives. Note: Even if your phone is outside the company network (on external internet), Linkus relies on Apple Push Notification service (APNs) to alert you of incoming calls. If push is blocked or fails, no ringing occurs—but the call is still logged as missed in the PBX. Verified Solutions: Option 1: Ensure Push Notifications Are Enabled on PBX Log in to your PBX admin portal. Go to Extensions > [Your Extension] > Linkus Settings. Confirm that "Accept Push Notifications" is enabled. If disabled, the PBX will not send push alerts to your device, and mobile.log will show: presence set client not allow push. Option 2: Check Linkus App Settings on Your iPhone Open the Linkus app. Go to Settings (gear icon) > Push Notifications. Make sure "Stop Push Notifications" is OFF. If enabled, the PBX logs will show: client set silent, not push. Option 3: Re-launch Linkus After PBX Upgrade If your PBX was recently upgraded to firmware version 83.22.0.134-beta1 or later (e.g., 83.22.0.138/139, 37.22.0.138/139, or 84.22.0.138/139), and you had previously force-quit the Linkus app, you must manually reopen Linkus once after the upgrade to re-establish push registration. Known Issue (Fixed in V23.3-GA): In versions prior to 83.22.0.138 (P-Series Software), if Linkus Mobile was killed before upgrading, push notifications would stop working until the app was relaunched. This is resolved in V23.3-GA, but affected users still need to open the app once post-upgrade. Option 4: Verify iOS System Permissions Go to iPhone Settings > Notifications > Linkus. Ensure Allow Notifications is ON and Sounds are enabled. Also check Settings > Linkus > Background App Refresh is enabled. Additional Recommendation: Ensure your PBX is running the latest V23.3-GA firmware (e.g., 83.22.0.139 for P-Series Software Edition), as it includes critical fixes for push notification reliability and security enhancements. Immediate upgrade is strongly recommended. If the issue persists after applying the above steps, collect PBX mobile.log and send us a detailed description of your problem for our technical support team (helpdesk@yeastar.com) to review. Thank you for your support and understanding.
COPY AND PASTE!
Response from developer
Thank you for your feedback regarding the Linkus iOS App chat experience. These are product-level limitations based on the current version of Linkus for iOS. While your suggestions align with common user expectations, they require feature enhancements that are not yet implemented. We recommend submitting this feedback directly through the Yeastar official support channel (helpdesk@yeastar.com) so it can be forwarded to the product team for future consideration.
