Call stuck in SP1

[njtsnet]

We are running 16.0.493 with grandstream phones GX2160 1.0.9.135 (as of today they are outdated I guess new firmware is now recently supported)

Had a complaint that a extension was not ringing, phone looked normal, but in the active calls on the server it shows a call to SP1, There was nobody in SP1 (we use the hardware keys and shared parking BLF keys)

We could not clear it by hitting the x nor any other tricks we tried. We deleted the extension and re-created, which was the workaround without rebooting the server. It's still shows in the active call screen but it no longer tied to caller 1008 ext. and is blank shows no caller -null (pics below) will reboot after hours,. assuming others may of seen this issue before would like to know what circumstances cause this issue, so I can prevent future stuck calls like this.

 

[cobaltit]

When you click X did it give you an error or any sort of response?

 

[njtsnet]

No response no errors when clicked

 

[cobaltit]

Hmm.. that is weird. Try a different browser perhaps? Otherwise I guess waiting for a server reboot it is. Never had that happen as far as I can recall. What is your dial tone source?

 

[njtsnet]

will try another browser using chrome now. Sip is twilio

 

[njtsnet]

tried firefox and edge no response.

 

[YiannisH_3CX]

Stuck calls could happen for a number of reasons and we won't know what the reason is until we look through the PBX logs. If this was an one time occurrence i would not worry about it. If it happens again then you should investigate more. The activity log and verbose logging should help you in this matter.
To clear the call try restarting the SIP server service and see if that helps. Please note that all active calls will drop by restarting the service.

 

[njtsnet]

Thanks yes last night I just restarted all the services and it’s cleared up. Hoping it was just a one time event. It’s a busy pbx around 700 calls an 8hr day day so turning on verbose logging causes some concerns during active hours.

 

[YiannisH_3CX]

I agree that verbose logging should be off as it can quickly deplete resources on a low end machine. But with a good machine you can turn it on if the issue comes back so you can troubleshoot. You can adjust it to only keep files for a day and turn it off when you catch the issue.
But since this only happened once i would not worry.