Hi,
Installed FreePBX 17 and it seemed to go OK. Restored latest backup from FreePBX 16.
However CLI constantly displays the following ERROR:
ERROR[1982]: res_pjsip.c:903 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport ‘0.0.0.0-udp’
PJSip Settings: YES is enabled for the IP address for UDP and the port 5060
What might be causing the error to constantly be spewed in CLI ?
Thanks.
have you checked at OS side Port 5060 is opened or not ?
netstat -ntlup | grep 5060
Hi, in /etc/asterisk/pjsip.endpoint.conf the file contains all what appears to be trunk settings, all [trunk name] have:
transport=0.0.0.0-udp
Where is that setting in the UI??
Thanks.
no check that command at Debian OS CLI side.
udp 0 0 xx.xxx.xxx.xxx:5060 0.0.0.0:* 1816/asterisk
netstat -ntlup | grep 5060
udp 0 0 0.0.0.0:5060 0.0.0.0:* 2007/asterisk
try to change ip ^^ to 0.0.0.0
Hi, that is where the 0.0.0.0-udp is
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
/etc/asterisk/pjsip.endpoint.conf:transport=0.0.0.0-udp
Hi,
I put xx’s to conceal the guilty party 
pjsip.endpoint.conf transport=0.0.0.0-udp is more for sip trunk or for users.
have you checked at pjsip.transports.conf side.
Hi there,
I have the exact same issue. Since I did an install of 17 and restored my backup. My trunks connect to the providers as they are registered. However, I can’t see any incoming calls on the Log as it just states:
ERROR[1918] res_pjsip.c: Unable to retrieve PJSIP transport ‘192.168.0.35-udp’
When I try to call, it never rings and is silent. I have spent weeks trying to find a solution. I really hope someone could shed some light on this for me.
Thanks
Hi Curtis,
I went back to the VM running 16 although the FreePBX 17 VM is running, nothing is actually pointed to it. I think the problem stems from having SIP trunks because the default PJSIP port is 5060. Even in FreePBX 16 I was seeing similar errors.
To get rid of the errors, disabled all sip trunks and renamed each trunk with its same name-sip and then created PJSIP trunks for each. There are no more errors in CLI period. Next step is take a backup of the FreePBX 16 server, remove all the trunks in the FreePBX 17 server and then do a restore in FreePBX 17.
However I still have an issue with IPTABLES in the Debian 12 OS. In previous versions of FreePBX whether Centos or Sangoma OS’s my firewall script worked perfectly. In Debian it is completely different and even systemctl list-unit-files shows iptables as an alias. IPTABLES is not enabled on a reboot and if I remove any IP address in our firewall script, iptables -nL does not show it.
I am not saying there is anything wrong with Debian 12, clearly it’s my lack of experience with the OS.
In the current OS releases of Linux, including Debian, iptables has been replaced with nftables. However, iptables still exists with an API into nftables. The iptables commands work just fine. You need to show the errors or this script so we can see what is happening with it.
