Teams Calls stopping working

[Craig Stevens]

We have setup the 3CX and teams intergration and it works great, and then after a while it stops working. you can see on the server (Windows 2016) that 5062 is no longer listening for connections. if you restart the SIP service it starts working again for a while.

I do see in the Activity Log Teams destinations list is empty! any ideas?

 

[NickD_3CX]

Hi!

Could you tell us how you check that nothing is listening on 5062 when this happens?
Also whet version of 3CX server are you currently running?

 

[Craig Stevens]

"netstat -an" when you first start the sip service you can see it listening on 5062 but then after a while it stops.

We are on 3cx 18.0.1.234

 

[NickD_3CX]

Is there any other software on the Windows Server that could be interfering, like any AV or network security software?
If the port is forced closed by some other application, that could explain this behavior.

Also is there a fixed interval between you restarting the service and this happening?
If you have an approximate time frame, do the Windows Event Logs show anything around that time when 3CX Stopped listening?

 

[Craig Stevens]

No there is nothing interfering that I can think of.

The interval doesn't seem to be fixed, it has failed after half and hour or lasted all night.

There is nothing in the eventlogs that relates, but I am still monitoring. I am not sure what should be usually behaviour but running a "netstat -an | findstr 5062" I can see that the connections are not closing down after the calls have terminated currently have 10 open connections on 5062 and no calls in progress. is this expected behaviour?

 

[Craig Stevens]

in fact ignore the connections they do close down after a while. it seems stable at the moment, if it fails again I will try and get more details.