Hi 3CXers, I have an issue with call groups. I am running 3CX 3.0.2328.0 on a test server. I have 2 extensions, 201 and 202 and two hunt groups 800 and 801. 800 has only 201 as a member and is set as ring all, ring time 8 seconds, destination if no answer is set to 801. 801 has 201 and 202 as members and is also set on ring all, ring time 30 seconds, destination on no answer continue ringing. I also have one SIP line set to call 800. The trouble is that when the call leaves the first hunt group 800 and enters the second 801 the call alerting to 201 is momentarily stopped. This behaviour results in a missed call appearing on the handsets call history, when, as far as the user is concerned, no call was missed. It also leaves open the possibility that someone could pick up the handset in the brief interval between the call stopping ringing and starting ringing again, and therefore not be connected to the incoming call. Although after some attempts I have been unable to get this to happen. It also does exactly the same with Queues instead of Hunt groups. Actually we used to have this issue with the Avaya IP Office until the behaviour was changed in a firmware update years ago. It's quite a common scenario in a small office; you want the calls to go the junior people first, but if they are not able to take them you want them to go to the less junior people, whilst continuing to alert on the junior people’s handsets in case they get back to their desks. Can anyone reproduce this? It would be better if the hunt group or queue looked ahead to the hunt group or queue it was going to overflow to and did not stop alerting any stations that were in the second group or queue. Chris.