I know this forum is primarily for the actual 3CX client app, however I've found that in the past to not be 100% reliable for incoming calls, sometimes it goes to sleep or doesn't re-register when bouncing between WiFi and 4G, so I have set up my SIP extension using the built in native Android SIP function of my mobile phone. Initially I thought it was working great, it seemed to always register itself (and stay registered) and incoming calls were never an issue, if my desk phone was ringing, no matter where I was my mobile would also ring. If someone dials my extension directly, I can pick up the call on my mobile and it works fine. However, I am also an agent in a queue on our 3CX system. If someone calls the queue, they are greeted with a message "someone will be with you shortly" and then placed on hold. All agents extensions then begin to ring as normal, however whenever I try to answer the call on my mobile, I swipe to answer (like a normal mobile call), it appears to pick up the call and show the duration on my screen of 0:00, then it cuts out and my phone begins to start ringing over again. No matter how many times I try to answer it, the call drops then my phone starts ringing. Just to clarify, the caller has no idea this is going on, they are hearing hold music the whole time - it doesn't disconnect them, it just doesn't let me pick up the call. Using the 3CX native app, I can answer queue calls fine - just not with the native Android SIP. Has anyone come across this before and know if there's a fix or workaround? I'd love to continue using native SIP if possible but if I can't answer queue calls unfortunately I'll have to go back to the official 3CX app.