TIPS PJSIP/anonymous-00000008", "Received incoming SIP connection from unknown peer to NUMBER

[cantVOIP]

I'm moving away from CHAN_SIP to PJSIP.
I've changed PJSIP to listen to 5060 and CHAN_SIP to listen to 5160.
Changed all extensions to PJSIP
Created appropriate Trunks
Added new trunks to Outgoing calls, and Incoming calls are set to ANY.
I've restarted the console, the machine too.

The issue arises when I try to call any of my numbers. I get the number is not in service on the phone, and in the logs I get:
PJSIP/anonymous-00000008", "Received incoming SIP connection from unknown peer to NUMBER"

It appears as if the connection between my ATA and the PBX shows it as anonymous.
I have a single ATA that works as intended out of the 7 I have. They are all configured the same ATAs and Trunks.
I have double, triple verified this. If I set allow anonymous calls the connection is successful, however, I wouldn't want to keep this option on.

Any idea as to why this is happening, or what I am missing?
I find it weird that a single ATA (line) is recognized but the rest are marked as anonymous.

Thank you for your help!

 

[dallas]

I have a single ATA that works as intended out of the 7 I have. They are all configured the same ATAs and Trunks.

Are you certain they are all the same?
There's not much information in your post to help diagnose the issue.

What version of IncrediblePBX are you using?
Are the ATAs registering the the PBX?
Have you whitelisted the ATAs IP addresses?

 

[cantVOIP]

What version of IncrediblePBX are you using? Have you whitelisted the ATA IP addresses?

I'm using incrediblePBX 2021.
Yes, I've whitelisted my network 192.168.x.x/24 using ip table command, and even specifying each ATA's IP individually. Restarted IPtables and the console.
I've also added my network in the GUI under local network. None of the prior worked

 

[kenn10]

If you changed your trunks to PJSIP, you must whitelist the IP addresses of your incoming providers and also show them in the PJSIP trunk's "Match" field. If PJSIP doesn't see them in the match field, it assumes they are unknown. I can't tell by your post if you have incoming trunks on the ATA's or have actual sip trunks coming into the system.

 

[Samot]

If you changed your trunks to PJSIP, you must whitelist the IP addresses of your incoming providers and also show them in the PJSIP trunk's "Match" field. If PJSIP doesn't see them in the match field, it assumes they are unknown. I can't tell by your post if you have incoming trunks on the ATA's or have actual sip trunks coming into the system.

Chan_PJSIP, unlike Chan_SIP, doesn't have a default anonymous or outbound trunk. If there are no matches for a Chan_PJSIP endpoint then the call would be rejected unless an anonymous endpoint was created which it looks like one is created. The only way that gets created in FreePBX/IPBX is if Guest Calling/Anonymous Calling is enabled.

 

[wardmundy]

@cantVOIP: As a last resort, try adding a line like the following for each of your DIDs (as shown for NUMBER) to the top of the [from-sip-external] context in /etc/asterisk/extensions_override_freepbx.conf:

[from-sip-external]
exten => 8881234567,1,Goto(from-trunk,${DID},1)

If the [from-sip-external] context isn't already in the override file, you can cut-and-paste it from extensions.conf to begin.

Then fwconsole reload. Be sure to add an incoming route for each of the DIDs in the FreePBX GUI as well.

 

[cantVOIP]

If you changed your trunks to PJSIP, you must whitelist the IP addresses of your incoming providers and also show them in the PJSIP trunk's "Match" field. If PJSIP doesn't see them in the match field, it assumes they are unknown. I can't tell by your post if you have incoming trunks on the ATA's or have actual sip trunks coming into the system.

I've whitelisted one of my ATAs in the server directly, and made sure the specific IP address is listed
iptables -nL
ACCEPT all -- 192.168.x.x 0.0.0.0/0

I've added the same IP 192.168.x.x/32 under the Match (Permit) section of the trunk and then fwconsole reload.

I have a catch all inbound route. But for this troubleshooting I added a specific inbound route for this number:
Description: 888-888-8888
DID Number: 8888888888
CallerID Number: 8888888888

I'm still getting the same anonymous message in the logs

 

[cantVOIP]

Chan_PJSIP, unlike Chan_SIP, doesn't have a default anonymous or outbound trunk. If there are no matches for a Chan_PJSIP endpoint then the call would be rejected unless an anonymous endpoint was created which it looks like one is created. The only way that gets created in FreePBX/IPBX is if Guest Calling/Anonymous Calling is enabled.

My outbound trunks are setup and the ATAs are registered to the PBX.
I've enabled anonymous calling temporarily to allow inbound calls to the PBX and not be rejected.
I am trying to get the PBX to recognize the ATAs and not mark them as anonymous.

 

[wardmundy]

@cantVOIP: Unless you've won the lottery, you don't want to enable anonymous calling.