No incoming call

FreePBX Endpoints
1

Hello
I have freepbx 16 with only one trunk (fxo grandstream gxw4108 192.168.1.aaa)
I have no problems with outging call, but i dont receive any incoming calls

Peer details:
username=9001
type=peer
secret=strong_secret
qualify=yes
nat=no
insecure=invite,port
host=192.168.1.aaa
fromuser=9001
fromdomain=192.168.1.aaa
canreinvite=no
allow=alaw,ulaw

With sip show peers I have trunk status OK
But in logs a have the next:

[2024-04-24 15:12:20] NOTICE[22652]: res_pjsip/pjsip_distributor.c:676 log_failed_request: Request ‘REGISTER’ from ‘sip:9001@freepbxIP’ failed for ‘192.168.1.160:5060’ (callid: 0ad7b22459873092d5518fa284361211@freepbxIP) - No matching endpoint found
[2024-04-24 15:12:20] NOTICE[22652]: res_pjsip/pjsip_distributor.c:676 log_failed_request: Request ‘REGISTER’ from ‘sip:9001@freepbxIP’ failed for ‘192.168.1.160:5060’ (callid: 0ad7b22459873092d5518fa284361211@freepbxIP) - Failed to authenticate

What is confusing me - res_pjsip/pjsip_distributor

Can anybody help me?

2

The incoming calls are being handled by chan_pjsip, but you have only configured the obsolete chan_sip. When both exist, FreePBX prefers chan_pjsip for the standard SIP port 5060.

The preferred solution is to remove chan_sip and do all your SIP endpoints with chan_pjsip.

3

My extensions are PJSIP, but trunk supports only SIP.
Can I force to specify using SIP on trunk?

4

Extremely unlikely to be true.

You will need to tell the other end of the trunk that they need to talk to port, I think, 5070, not the default port 5060. If you are registering with them, and they are sending to port 5060, their SIP implementation is broken (or you have a broken router).

In certain network configurations, it may be possible to bind the two to specific interfaces, but this will confuse anyone who maintains it, in future.

If it is really impossible for them to work with chan_pjsip, you need to provide detailed reasons, so the Asterisk developers know what they have to change, to make it work.

5

Oh, thx… changing the port solved the problem!

6

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