I’m seeing-
[2023-04-05 11:50:48] WARNING[1909] res_pjsip_outbound_registration.c: No response received from ‘sip:holtain.intervoip.co.uk:5060’ on registration attempt to ‘sip:[email protected]:5060’, retrying in ‘60’
And I think it might be because no request is sent as I’m seeing no traffic on port 5060 apart from connections from a Yealink W70B which is why I’m excluding 10.0.0.45
tcpdump -vv -s 4096 port 5060 and not host 10.0.0.45
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 4096 bytes
I don’t work on or use FreePBX, so someone else will have to give a recommendation on how to achieve that in FreePBX. I can just say from an Asterisk perspective what needs to happen.
You’ll need to check with your VoIP provider to see from them what fqdn you should use in that trunk that’s an A record and not an SRV record. If they don’t have a preference maybe you could try using one of the ones that are inside the SRV record?
If with SIP Server Port left blank, you still cannot register, at the Asterisk command prompt type pjsip set logger on
wait two minutes, paste the Asterisk log showing the failed registration attempt at pastebin.com or similar, and post the link here.
OK I think leaving the port blank has fixed it
[2023-04-06 07:41:18] VERBOSE[8225] res_pjsip/pjsip_options.c: Contact TestCIX/sip:[email protected] is now Reachable. RTT: 69.186 msec
So I take it we’re connected even though I’s still seeing
[2023-04-06 07:41:40] WARNING[8225] res_pjsip_outbound_registration.c: No response received from ‘sip:[email protected]:5060’ on registration attempt to ‘sip:[email protected]’, retrying in ‘60’
Maybe. If Asterisk Info → Registries doesn’t show the trunk as Registered, there is still a problem. On the Advanced tab for the trunk, confirm that Client URI and Server URI are both blank. If that’s not your issue, please paste the Asterisk log for a failed registration (with pjsip logger on), as requested earlier.
