Strange behavior when I call a connecting extension

[Francoleddu]

I recently installed version 16 and something doesn’t work like before.

Situation with version 15:
an internal extension (660) makes a call to my mobile; if a second internal extension (601) calls the first while calling (waiting for answering), the call in progress is interrupted and the 660 answers the 601.

Situation with version 16:
same conditions, but when 601 calls 660, the extension is busy and therefore 601 does not connect to 660.

Is there any setting I can change to have the same previous behavior?

My configuration:

• Raspberry PI 3B+
• Raspbian GNU/Linux 10
• FreePBX 16.0.26
• Asterisk 16.21.1

[david55]

Could this have the same underlying cause as:

Ring group behaviour change after 16.0/chan_pjsip upgrade

We’re in the process of upgrading our PBXs, and have found some behaviour changes in ring groups I’m hoping we can fix somehow. The old PBX (FreePBX 15, Asterisk 13, chan_sip) had a ring group with 3 extensions and ringall strategy. If one of the extensions was on the phone, calls would still go to it, with the option to answer. Log entries: [2022-12-27 09:52:13] VERBOSE[32630][C-00000219] res_agi.c: Launched AGI Script /var/lib/asterisk/agi-bin/dialparties.agi [2022-12-27 09:52:13] VERBOSE[32…

[Francoleddu]

david55, thank you for your suggestion!
Unfortunately I won’t be able to test before the weekend.
I will keep you up to date.

[Francoleddu]

Yesss, now it works!
david55, thank a lot again you for your suggestion