Trunk and inbound call issue

Greetings Everyone,

I have been working on freePBX for the few days now But there has been an issue. I have settled up a trunk and inbound Route to an extension but not have been able to see the call flowing to that extension here

The trunk shows as available when I use pjsip show endpoints

Here are the logs of /var/log/asterisk/full when I call:

[2022-06-30 02:45:02] NOTICE[24610] res_pjsip/pjsip_distributor.c: Request 'INVITE' from '<sip:[email protected]>' failed for '209.216.2.211:5060' (callid: [email protected]) - No matching endpoint found
[2022-06-30 02:45:05] NOTICE[24610] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '156.146.50.108:54784' (callid: e5f4a185506585e4f7a) - No matching endpoint found 
[2022-06-30 02:45:05] NOTICE[17119] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '156.146.50.108:54784' (callid: e5f4a185506585e4f7a) - No matching endpoint found 
[2022-06-30 02:45:05] NOTICE[17119] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '156.146.50.108:54784' (callid: e5f4a185506585e4f7a) - Failed to authenticate
[2022-06-30 02:45:05] NOTICE[24610] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '156.146.50.108:54784' (callid: e5f4a185506585e4f7a) - No matching endpoint found 
[2022-06-30 02:45:05] NOTICE[24610] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '<sip:[email protected]>' failed for '156.146.50.108:54784' (callid: e5f4a185506585e4f7a) - Failed to authenticate

It says no matching endpoint which would suggest that the number in the inbound route doesn’t match the number presented by the trunk.

I have matched all the DIDs in inbound route Means any DID number

No matching endpoint happens even before the dialplan is invoked. It isn’t a DID problem.

Is the blue splodge the same as 209.216.2.211? What are the match/permit settings?

Hmm I have not setted any match or permit settings

If inbound calls on this trunk come from multiple source IPs/subnets, then each needs to be listed on the trunk match permit line in the trunk advanced tab.

You can also provide network specifications as network address / netmask or number of bits on left, e.g. 192.168.1.0/24 or 192.168.1.0/255.255.255.0. They don’t have to match the actual network structure.

1 Like

Yes, you’re correct. That will teach me for trying to be helpful too early in the morning on the train!

Thank you everyone I Found the solution The solution was to setup the sip servers IP from which I am calling to the permit section in the trunk I have created

Is there a way to allow all IP in match/permit ?

You wouldn’t want to do that as it will allow bad traffic through as well as the good.

chan_pjsip has an anonymous match option, but whilst it was sometimes necessary to do that on can_sip, chan_pjsip allows multiple network ranges to be set in match/permit, which is a much safer option.

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