Source address … does not match identify …

Hi all!

I have a strange problem. My FreePBX 15.0.16.65 is up and running.
Since some weeks I have now an issue that incoming call don’t work anymore. A call

rasterisk -x “core restart gracefully”

does solve the issue. I activated detailed logging and the difference is

— OK —
[2020-07-16 09:25:22] DEBUG[3354]: res_pjsip/pjsip_distributor.c:384 find_dialog: Could not find matching transaction for Request msg INVITE/cseq=8473204 (rdata0x7efcbc013978)
[2020-07-16 09:25:22] DEBUG[3354]: res_pjsip/pjsip_distributor.c:462 ast_sip_get_distributor_serializer: Calculated serializer pjsip/distributor-00000041 to use for Request msg INVITE/cseq=8473204 (rdata0x7efcbc013978)
[2020-07-16 09:25:22] DEBUG[3355]: netsock2.c:172 ast_sockaddr_split_hostport: Splitting ‘217.0.26.195’ into…
[2020-07-16 09:25:22] DEBUG[3355]: netsock2.c:226 ast_sockaddr_split_hostport: …host ‘217.0.26.195’ and port ‘’.
> [2020-07-16 09:25:22] DEBUG[3355]: res_pjsip_endpoint_identifier_ip.c:255 ip_identify_match_check: Source address 217.0.26.195:5060 matches identify '051xxxxx30’

— ERROR ----
[2020-07-16 09:24:02] DEBUG[11988]: res_pjsip/pjsip_distributor.c:384 find_dialog: Could not find matching transaction for Request msg INVITE/cseq=6594444 (rdata0x7f395c0d48d8)
[2020-07-16 09:24:02] DEBUG[11988]: res_pjsip/pjsip_distributor.c:462 ast_sip_get_distributor_serializer: Calculated serializer pjsip/distributor-00000048 to use for Request msg INVITE/cseq=6594444 (rdata0x7f395c0d48d8)
[2020-07-16 09:24:02] DEBUG[17685]: netsock2.c:172 ast_sockaddr_split_hostport: Splitting ‘217.0.26.195’ into…
[2020-07-16 09:24:02] DEBUG[17685]: netsock2.c:226 ast_sockaddr_split_hostport: …host ‘217.0.26.195’ and port ‘’.
> [2020-07-16 09:24:02] DEBUG[17685]: res_pjsip_endpoint_identifier_ip.c:260 ip_identify_match_check: Source address 217.0.26.195:5060 does not match identify '051xxxxx30’

I need a clue why ip_identify_match_check may fail. The configuration seems to be Ok because it works generally but somehow it does fail after some time…

Also a clue how to debug this further would be helpful.

TIA,

HS

Use “pjsip show identify” in the Asterisk CLI to look at the current configuration when it does fail.

1 Like

Ok. Thanks. So I have to wait some time until it does fail again.
I will use

pjsip show identifies
and
pjsip show identify 051xxxxx30

and report back.

Now I got the issue again. While not working I got

asterisk*CLI> pjsip show identifies

 Identify:  <Identify/Endpoint...........................................................>
      Match:  <criteria...........................>
========================================================
 Identify:  051xxxxx30/051xxxxx30
      Match: 217.0.26.195/32
      Match: 217.0.26.197/32
      Match: 217.0.26.67/32

and after a restart of asterisk:

asterisk*CLI> pjsip show identifies

 Identify:  <Identify/Endpoint...........................................................>
      Match:  <criteria...........................>
========================================================
 Identify:  051xxxxx30/051xxxxx30
      Match: 217.0.129.229/32
      Match: 217.0.129.227/32
      Match: 217.0.26.69/32

Where is my configuration error in the pjsip configuration?

TIA,

HS

I don’t know FreePBX, but I think it is configuring as a hostname. The hostname may resolve to different IP addresses at different times. One way to resolve it would be to explicitly configure all the possible IP addresses. @lgaetz probably can point you to the right part of the UI.

1 Like

Need to know the contents of the PJSIP host and Match (Permit) fields for your pjsip trunk.

1 Like

Not sure where to look for “PJSIP host”.
“SIP Server” is “reg.sip-trunk.telekom.de
“Server URI” is “sip:sip-trunk.telekom.de”
My “Match (Permit)” is empty.

This is your issue. Your provider has multiple signalling servers from which calls can originate. You must populate ALL of them in the Match (permit) field as IPs, subnets and/or fqdns. The provider can give you this list.

If you’re using the PBX Firewall module, you will have to whitelist all those entries as well.

1 Like

Thanks. I will try and respond in a few days.

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