Solved Conference Calls Not Hanging Up

[architechture]

Hello All,

I have an ongoing issue with a client tenant that has me stumped. It seems that almost every time that the do phone initiated conference, after they hang-up, the 2 calls conferenced in in stay on the conference extension (70 in this case). I've seen them show the call is active for 30 to 60 minutes after. And of course this is a small tenant 4sc so they often can't make or take calls because all lines are full. Has anyone seen this before? Do you think it's some odd way that the conferencing extension hangs up on the call?

Thanks, Shawn

 

[VasilisV_3CX]

Hi @architechture,

How are they hanging up the calls? What clients / devices are being used in the conference?

 

[architechture]

They say they just hit the speakerphone button to hang up. Phones are a are a mix Yealink T48s/g. This happened on v16 and now on v18 running on windows server.

 

[NickD_3CX]

How are these phones connected/configured with the 3CX, Local LAN (same network as the 3CX server), Remote STUN or using a 3CX SBC?

 

[architechture]

STUN - Remote

 

[ChrisC_3CX]

I have to say, we usually recommend against using STUN configuration if it can be helped and opt for using the 3CX SBC instead. STUN configuration is a bit tricky to get right sometimes and not doing so may result in unexpected behavior. Since you mention this happens almost every time, it should be easy enough to check if this is due to the provisioning method used by testing with 3CX clients instead of the IP Phones for a while.

If by testing with 3CX Clients (3CX Webclient, Desktop App, etc) you cannot reproduce it, I'd strongly recommend you take a look at the following guide and make sure you haven't missed anything when the IP Phones were deployed: https://help.3cx.com/help/en-us/9-ip-phones/197-why-are-my-stun-phones-not-working

Better yet, I'd recommend setting up an SBC instead, especially if you have more than one IP Phone on the same site. Using the 3CX SBC will not only ensure smooth IP Phone operation but also make provisioning much easier and also add a layer of security due to the utilization of the 3CX Tunnel.

 

[architechture]

I had some overlap in ports. I think this is resolved now. Thank you!

 

[ChrisC_3CX]

Brilliant!

Happy to see you managed to sort this out! Do let us know should anything else come up!