New SIP Trunk request register failed to authenticate x1000

FreePBX Providers
1

Can call outbound. Cannot call inbound.

Had copper lines on a vega that worked fine. Switch to SIP Trunk over the internet. Authenticates fine with the SIP trunk and calls outbound are fine. But inbound calls fail and this message spams the Asterisk log files (below). I’ll try to add the file, but it is just this line 1000 times. I saw something about PJSIP vs CHAN PJSIP. I see PJSIP on the trunk that authenticates good, but I see CHAN PJSIP as the only tab in Asterisk SIP settings. I see a setting area at the bottom of that screen. Listening on 5060. But the trunk uses sip server port 5080. I see other fields asking for external IP and signaling port. Should I put the IP of realmconnect and port 5080 there? I am not sure about “domain the transport comes from.”

Authentication in the trunk is set to outbound. Registration is set to send. And that seems good, since I can call outbound.

NOTICE[10696] res_pjsip/pjsip_distributor.c: Request ‘REGISTER’ from ‘“1001” sip:[email protected]’ failed for ‘103.176.90.16:12615’ (callid: 866720488) - Failed to authenticate

SIP Trunk is with RealmConnect in Georgia. They mostly work with Avaya and are not sure how to help.

Any help is greatly appreciated! For a school.

2

Given that 103.176.90.16 is at a cloud provider in Hong Kong, the failed register requests are most likely attempted attacks, or possibly a misconfigured system that is inadvertently hitting your PBX.

In any case, they are unrelated to your inbound issue. You most likely don’t need any of the special settings on the pjsip tab of Asterisk SIP Settings. However, on the General tab, make sure that External Address and Local Networks are correctly set. If you change these, after Submit and Apply Config you must restart Asterisk.

If that’s not your issue, what if anything appears in the Asterisk log on an attempted incoming call? If nothing, run sngrep and report what if anything appears there.

3

Stewart,

Thanks so much. I blocked all IPs but the 1 Realm Connect said was theirs. I added the external and internal IP in the area suggested and rebooted the whole PBX. Is that the same as rebooting Asterisk? After that I get the same messages about no matching endpoint and failed authentication. I changed the persons caller ID name, phone number, and IP, but this is what it looks like. 200 lines of the first one, then 200 lines of the second one.

[2025-07-18 16:07:16] NOTICE[2731] res_pjsip/pjsip_stributor.c: Request ‘INVITE’ from “NAME NAME" sip:[email protected]’ failed for ‘162.222.151.25:5080’ (callid: 20250718200715014673-84980a6a83867bb9db0a3ba9ba0d5b47) - No matching endpoint found after 5 tries in 0.436 ms

[2025-07-18 16:07:49] NOTICE[2731] res_pjsip/pjsip_distributor.c: Request ‘INVITE’ from “NAME NAME" sip:[email protected]’ failed for ‘162.222.151.25:5080’ (callid: 20250718200748031465-84980a6a83867bb9db0a3ba9ba0d5b47) - Failed to authenticate

4

Yes[quote=“PhonesRaHeadache, post:3, topic:106645”]
Is that the same as rebooting Asterisk?
[/quote]
Yes, rebooting the server was fine.

I can’t make sense of your log entries, because you haven’t told us what the changed values represent.

Is this a number on your RealmConnect account, the caller’s number, or something you don’t recognize? If the last, post the actual value.

Is this your public IP, the IP address at RealmConnect to which you register, or something else? If it’s other than your public IP, post the actual value.

Is this your public IP, the IP address at RealmConnect to which you register, or something else? If it’s other than your public IP, post the actual value.

5

Realm Connect IP for both on port 5080. Registering / authenticating on 5080. IP 162.217.15.25:5080

The sip trunk is registered fine with that IP, but the incoming calls do not.

+1321802XXXX was someone’s phone number calling the school. Inbound call. So FreePBX can see the incoming call and phone number, but cannot find endpoint or authenticate.

Thanks for your interest.

6

Try setting Match (Permit) for your RealmConnect trunk to
162.217.15.25
Submit, Apply Config and retest.

7

Thanks so much! That worked! And for pointing out the bad IP addresses. Inbound calls are working!

8

I don’t understand why the proper “identify” didn’t get automatically created.
However, if you will be using Match (Permit), you should find out all the addresses from which RealmConnect will send calls and list them all. Otherwise, if they send a call from another server (failover, load balancing, etc.) it will fail.