Ring Groups not ringing

Understood. My observation is that the phones do not become unavailable, the Ring Group processing incorrectly sees the phones as unavailable. I will get a working log and a broken log to compare when next available.

It is my understanding that Apply Config restarts the PBX cold so I fail to see how rebooting fixes this.

Apply config does not restart anything, it just regenerates the dialplan among other things.

I have duplicated this situation on a second PBX server. Here is what the log says when Ring Group does not ring.

"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Caller ID name is ‘F1 SYSTEMS’ number is ‘+13034640033’ "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: CW Ignore is: "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: CF Ignore is: "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: CW IN_USE/BUSY is: 1 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Methodology of ring is ‘ringall’ "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Added extension 201 to extension map "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Added extension 202 to extension map "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Added extension 203 to extension map "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Added extension 205 to extension map "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 201 cf is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 202 cf is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 203 cf is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 205 cf is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 201 do not disturb is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 202 do not disturb is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 203 do not disturb is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Extension 205 do not disturb is disabled "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Discovered PJSIP Endpoint PJSIP/201 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Ended up with no PJSIP contacts "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: dbset CALLTRACE/201 to 13034640033 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Discovered PJSIP Endpoint PJSIP/202 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Ended up with no PJSIP contacts "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: dbset CALLTRACE/202 to 13034640033 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Discovered PJSIP Endpoint PJSIP/203 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Ended up with no PJSIP contacts "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: dbset CALLTRACE/203 to 13034640033 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Discovered PJSIP Endpoint PJSIP/205 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Ended up with no PJSIP contacts "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: dbset CALLTRACE/205 to 13034640033 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Filtered ARG3: 201-202-203-205 "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: Setting default NOANSWER DIALSTATUS since no extensions available "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: RVOL_MODE ‘’ "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: RVOL is: "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: dialparties.agi: RVOLPARENT is: "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] res_agi.c: <PJSIP/Flowroute-000000a5>AGI ""Script dialparties.agi completed returning 0 “” "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] pbx.c: Executing “”[[email protected]:8] NoOp("""“PJSIP/Flowroute-000000a5"”"" Returned from dialparties with no extensions to call and DIALSTATUS: NOANSWER) in new stack “” "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] pbx.c: Executing “”[[email protected]:9] MacroExit("""“PJSIP/Flowroute-000000a5"”"" ) in new stack “” "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] pbx.c: Executing “”[[email protected]:19] Gosub("""“PJSIP/Flowroute-000000a5"”"" sub-record-cancel s 1()) in new stack “” "
"[2019-12-13 10:17:50] VERBOSE[7903][C-0000009e] pbx.c: Executing “”[[email protected]:1] Return("""“PJSIP/Flowroute-000000a5"”"" ) in new stack “” "

First, go to Asterisk SIP Settings -> SIP Settings [chan_pjsip] and confirm that Allow Transports Reload is set to No. If that’s not applicable or changing it doesn’t help, please report the simplest thing that fails.

When you are having the trouble, confirm that an internal call from an extension not part of the ring group directly to one of the ring group members succeeds, but dialing the ring group number from the same extension fails. If this is not the case, the trouble is in a different area from what you suspected.

Assuming that the above is ok, report whether
fwconsole restart
(rather than rebooting the whole PBX) gets the ring group working again. If not, reboot the PBX.

Next, open an unrelated page e.g. an extension in the admin GUI and press Submit without making any changes. Then press Apply Config. Report whether the ring groups have stopped working.

Thanks, that worked.

Asterisk SIP Settings - SIP Settings [chan_pjsip] - Allow Transports Reload was set to Yes and changing it to No seems to have solved the issue.

After editing the Ring Group it worked properly.

It appears that Allow Transports Reload is the culprit. What does this setting do?

It allows PJSIP Transports to be reloaded, instead of having to restart Asterisk to have changes apply. This is disabled by default in Asterisk itself and has to be explicitly enabled. This is because PJSIP does not fundamentally allow you to reload things, so the support uses a bruteforce approach which can sometimes fail.

Great info and that makes sense in context of what we observed.

Let me say how impressed I am with the responses here and the support provided. I hope I can be as helpful to someone in the future. Thanks all!

Warren
F1 Systems

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.