Ring groups do not work over trunks among two local PBX

General Help
1

I have set two FreePBX in local network for testing purposes. One PBX handles extensions numbered 1XXX, other handles 5XXX.

I have created few extensions on both PBX and also set Trunks and Outbound routes so any 1XXX extension can call any other 5XXX extension and back.

Then I have set Ring groups on each PBX numbered 1001 and 5001 respectively. Added few extensions to ring groups. For some time it all worked as expected, I could call any Ring group from any extension regardless of PBX as calls were routed as expected.

And then it just stopped working. I can call Ring group only from PBX where Ring group is created, meaning I can call 1001 from any 1XXX extension and 5001 from any 5XXX extension. But if I try to call 1001 from 5XXX extension (or call 5001 from 1XXX extension) I get message that number I dialed is not in service.

I do not recall I did anything in configuration that should disturb this. I checked configuration on both PBX and it seems it is all set as it should be.

This is strange, why trunks would allow extensions from two PBXes to call each other with no problem, but calls to ring groups fail? What could I do to make it stop working?

2

Paste the destination’s Asterisk log for a failing call at pastebin.com and post the link here. If nothing gets logged there, paste the log from the calling end.

3

Before test I checked:

1xxx extensions can call 5xxx extensions and 5xxx extension can call 1xxx extensions,

1xxx extensions cannot call 5001 ring group, neither 5xxx extensions can call 1001 ring group

Here is log of attempted call from 1116 to 5001.

Log is from PBX for 5xxx site.
PBX for 1xxx sit has no changes in log while attempting call.

4

While examining log I noticed this

[2025-06-16 16:38:57] WARNING[10811] res_pjsip_registrar.c: AOR '' not found for endpoint 'ToFreePBXUE-T1' (10.50.10.80:5060)	
[2025-06-16 16:38:58] NOTICE[661672] res_pjsip/pjsip_configuration.c: Couldn't find auth 'ToFreePBXUE-T1'. Cannot authenticate	
[2025-06-16 16:38:58] WARNING[661672] res_pjsip_outbound_registration.c: Failed to set initial authentication credentials	
[2025-06-16 16:38:58] WARNING[21409] res_pjsip_outbound_registration.c: '404' fatal response received from 'sip:10.50.10.80:5060' on registration attempt to 'sip:[email protected]:5060', retrying in '30' seconds

Similar shows on other PBX.

Maybe this is related?

5

Are these trunks trying to use registration? If not, they should be set Registration None, Authentication None. If registration is intended, one end should have Registration Send and the other Registration Receive (and username and secret configured).

Regarding the failed call, if the trunk name is correct, the Context for that trunk should be from-internal (it appears to be from-pstn or from-trunk). If the trunk name is incorrect, find out why the wrong trunk is matching.

6

I changed Context to from-internal and now it works. Thanks!

But it also worked when I first time set trunks and i left everything as default (default for Context is from-pstn) and later for some reason it stopped forking. That is what puzzled me.

I already tried to change Registration from Send to None and that made no change. It works now when I changed Context even if Registration is still set to Send.

Does this Registration influence security? Is it safe to have it set to None?

7

Registration Send doesn’t help (or hurt) anything, but causes some unwanted log entries. If you have set Registration None on both ends of all the trunks involved, I’d expect the error messages related to registration to be gone, but you’ll still need to set Context correctly.