Unable to retrieve PJSIP transport

FreePBX Providers
,
1

I have two trunks with my provider, as in my previous posts. I can call out fine.
Calling in takes a while and times out to “SIT this mobile number is unreachable”.
when opening asterisk -rvvvvvv I get the exact same message over and over:

[2025-06-09 09:49:23] ERROR[2398]: res_pjsip.c:763 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport '10.226.40.80-udp'

A bunch of times. This behaviour is deterministic for both of my phone lines.

Dialing between phonelines gives an “all circuits busy” recording.
Digging in the logs gives me “Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 38”. I think this is just because freepbx responds to some sip error wierdly. The root problem is not retrieving the PJSIP transport.

Please help?

2

Here is my pjsip.transports.conf

;--------------------------------------------------------------------------------;
;          Do NOT edit this file as it is auto-generated by FreePBX.             ;
;--------------------------------------------------------------------------------;
; For information on adding additional paramaters to this file, please visit the ;
; FreePBX.org wiki page, or ask on IRC. This file was created by the new FreePBX ;
; BMO - Big Module Object. Any similarity in naming with BMO from Adventure Time ;
; is totally deliberate.                                                         ;
;--------------------------------------------------------------------------------;
#include pjsip.transports_custom.conf

[192.168.1.110-udp]
type=transport
protocol=udp
bind=192.168.1.110
external_media_address=<REDACTED>
external_signaling_address=<REDACTED>
allow_reload=no
tos=cs3
cos=3
local_net=192.168.1.0/24

[10.226.40.80-udp]
type=transport
protocol=udp
bind=10.226.40.80
external_media_address=<SAME_AS_ABOVE>
external_signaling_address=<SAME_AS_ABOVE>
allow_reload=no
tos=cs3
cos=3
local_net=192.168.1.0/24
local_net=0.0.0.0/0
3

That isn’t a sensible thing to have in local_net

4

10.226.40.80 is the auto generated thing for the interface. It is an untrusted network and I don’t know the subnet. What should be here? 10.226.40.80/24 or something?

5

Does anything on you network use that IP space except for that interface?

6

Sounds to me as though it is not subject to NAT, so should not have any of the three NAT related address settings.

7

That interface goes straight to a vlan on my ONT, and is handled in my hypervisor. It is a dhcp network meant for ATA’s built into modems. I would like to repeat that outgoing calls work fine, but incoming doesn’t.

8

It is a private network run by my provider meant for ATAs built into modems. I do not own this network, nor know it’s network settings. I would like to repeat that outgoing calls work fine, but incoming doesn’t. Freepbx does not want to load the transport.

9

Specifying that every network is not subject to NAT and simultaneously specifying the NAT translated addresses is obviously wrong. It is possible that the 0.0.0.0/0 address is being faulted. It would definitely never be valid to use it. As far as I can tell, you have no NAT on that 10/8 network, so should not have public addresses, and should not have local networks.

However, in general, if something is being rejected, you should look at the startup logs, to see the reason given.