Upgrading PJSIP from 14.x to 17.x

I have four existing servers, 3 of which are running Asterisk version 14.2.1, and I have recently found the need to deploy a fifth server. I thought I would use this as an opportunity to explore the new version and I am hitting a wall with the PJSIP registration with my VoIP provider.

My existing PJSIP config looks like this for the provider trunk:

;==================================
; Provider trunk
;==================================

[wdp_reg]
auth_rejection_permanent=false
type=registration
outbound_auth=wdp_auth
server_uri=sip:sip.providerURL
client_uri=sip:$voipnumber@sip.$providerURL
contact_user=$voipnumber
retry_interval=10

[wdp_auth]
type=auth
auth_type=userpass
password=$voipPassword
username=$voipNumber

[wdp-trunk]
type=endpoint
transport=transport-udp
context=trunk-incoming
disallow=all
allow=alaw
outbound_auth=wdp_auth
aors=wdp_aor
direct_media=no
from_domain=$providerURL
from_user=$voipNumber

[wdp_aor]
type=aor
contact=sip:$voipNumber@sip.$providerURL:5060

[wdp_identify]
type=identify
endpoint=wdp-trunk
match=$providerIP/255.255.255.255

But I continue to get the following error:

[Feb 11 17:23:27] WARNING[913]: res_pjsip_outbound_registration.c:855 schedule_retry: No response received from ‘sip:$providerURL:5060’ on registration attempt to ‘sip:$voipNumber@$providerURL’, retrying in ‘60’

Now I have double checked, and the firewall is open on all the relevant ports on this server, and it can ping both $providerURL and $providerIP

These same setting work on the three other servers running Asterisk 14.x but I’m dead in the water on this server. I looked over the upgrade requirements but I didn’t see anything that would affect this. Have I missed something?

No, but it means just that - that it sent a REGISTER request and got not response. Did you do a packet capture to see if a response is coming back?

I ran packet capture on the interface and was getting no responses, but I did see some odd DNS resolution behaviour.
I ran out of time to work on this server and had to rebuild it as version I have proven as working before (Asterisk 14), but one of the changes I made during setup of the “new” server was to diable DHCP requests for nameservers, and lock resolv.conf as described here:

The “new” server registers SIP connections straight away. When I get back to my office I will run up a new install of Asterisk 17, and test whether the fault lies with the DNS issues, or some other version mismatch between my networking and the new packages.