Ring Groups: stage extensions does not go to stage 3

[duchotlineit]

I am having trouble with the ring group stage extensions.

I configured the call flow to start with an auto attendant(400), then a ring group(200) with three stages of 60 seconds each and the same extensions, then another auto attendant(401), and then back to the ring group(200). 

However, the ring group never reaches stage 3, and the call ends after the second ring, which also skips stage 3. All agents are active and available, but no one answers.

Can anyone offer any assistance or advice on this?

[Vodia PBX]

What is your "maximum ring duration (s)" (/reg_settings.htm)? If the duration is 60 seconds, it will probably cause those problems. BTW if you add the same extensions in all those groups, they will continue ringing as if they were in one stage.

[duchotlineit]

Hi 

Thanks for the fast reply

Yes it was on 60 seconds and now I have changed it to 600 seconds

there is still the hang-up after the second ring group call.

[RichardDCG]

I can confirm on V68.0.30 that even with a setting of 15 seconds it only loops once then drops the call. Almost like the system detects it is just looping and stops...

[Vodia PBX]

I would turn on the logging for the SIP packets and see what the phones reply. If they disconnect the call then that would explain it. Plus there is a known problem with the Windows app that is disconnects the call after 15 seconds, a new release is in the making that will fix that.

[RichardDCG]

The point is it doesn't matter what timer (15sec, 60sec, 120sec) you set, it doesn't proceed beyond the first loop - AA-RG-AA-RG-Stop.

[Vodia PBX]

Can you try taking the Windows app out of the equation? There is a known problem with the Windows app. For example, does it work better if you use a standard VoIP phone?

[duchotlineit]

same issue with a VoIP phone(I reduce the time to 1 min on the ring group)

[Vodia PBX]

We tested this here with Avaya J-series phones. After settings the maximum ring duration to ten minutes and the reprovisioning of the phones — it worked just as it should.

Can you double check if the phones send any 4xx responses while they should continue to ring? 

Also, for Yealink phones, what happens if you set the following value to the Yealink General parameter and retrovision the phones?

phone_setting.ringing_timeout=300

 

[RichardDCG]

On 10/28/2023 at 5:11 AM, Vodia PBX said:

it worked just as it should.

.. so it rang AA-RG-AA-RG-AA-RG-AA-RG ... etc until the caller hangs up?  It's not the duration of each stage, it's the looping of the call flow.

[duchotlineit]

Hi Admin,

We are having some trouble with the settings of the system.

Could you please guide us on how to modify them?

Thank you for your assistance.

[duchotlineit]

Hi,

Any Update?

[Vernon]

I don't think the PBX will allow you to loop the calls indefinitely with this scenario. There needs to be an exit strategy.

In the older versions there used to be a setting hidden in the .xml that was called max hops, maybe the new version has it as max loops. Take a look and maybe increase this value to be higher so the PBX will tolerate more hops/loops.

If you are using v68 and you want callers to "loop", you should be using the agent group instead of ring group. Then inside the agent group create your announcement messages, which i assume that's what the AA's are for.

[Brett Davey]

There is a modification to Duc's requirement and the flow now is AA-RG-AA-VoiceMail.

As has been previously pointed out the call does not proceed beyond the second ring group and never reaches VM. This is not an indefinite loop but a 2 stage flow using 2 ring groups only.

Our system is using v68.0.30 and there must be a way to increase the imposed flow limit.

[Vodia PBX]

You can change the global settings in the reg_settings.htm page without the need to restart, including the variable that limits the number of redirections (if that's the problem).