Supposedly a "DNS error for registration"

FreePBX Providers
1

Hi,

I have a working FreePBX 15.0.17.64 (fully updated to 03-01-22) which has 6 extensions and 3 trunks nicely configured. All three trunks are connecting to the same VOIP provider but 2 of them (1111111333 and 0000194) are complaining about supposedly trying to connect with UDP which is unsupported. Yet, nowhere do I have under the trunks or the inbound-outbound route configured to use UDP (all set to use TCP). The log is giving me a lot of these errors below and don’t quite understand why.

The extensions are working and phone calls seem to be routed correctly, even though my PBX is sitting behind a pfSense router/firewall that is NAT-ing.

Any thoughts?

Thanks

29013[2022-01-03 23:04:08] ERROR[1340] chan_sip.c: 'UDP' is not a valid transport for '0000195'. we only use 'TCP'! ending call.
29014[2022-01-03 23:04:08] WARNING[1340] chan_sip.c: Probably a DNS error for registration to [email protected], trying REGISTER again (after 20 seconds)
29015[2022-01-03 23:04:08] NOTICE[1340] chan_sip.c: -- Registration for '[email protected]' timed out, trying again (Attempt #52)
29016[2022-01-03 23:04:08] ERROR[1340] chan_sip.c: 'UDP' is not a valid transport for '1111111333'. we only use 'TCP'! ending call.
29017[2022-01-03 23:04:08] WARNING[1340] chan_sip.c: Probably a DNS error for registration to [email protected], trying REGISTER again (after 20 seconds)
29018[2022-01-03 23:04:08] NOTICE[1340] chan_sip.c: -- Registration for '[email protected]' timed out, trying again (Attempt #52)
29019[2022-01-03 23:04:08] ERROR[1340] chan_sip.c: 'UDP' is not a valid transport for '0000194'. we only use 'TCP'! ending call.
29020[2022-01-03 23:04:08] WARNING[1340] chan_sip.c: Probably a DNS error for registration to [email protected], trying REGISTER again (after 20 seconds)
29021[2022-01-03 23:04:08] NOTICE[1340] chan_sip.c: -- Registration for '[email protected]' timed out, trying again (Attempt #52)
2

Is there any reason why you need to use a deprecated channel driver?

Your text says 195 works, but your log shows if failing in the same way.

The probably a DNS error is a secondary error and is really saying “create_addr() failed”. That is failing because it checks the socket type, as well as trying to look up an address, and the socket type doesn’t match the specified restrictions, but I haven’t worked out why the socket type is set wrongly .

3

Well spotted, all three are “failing” in the log but correctly working. You mean “deprecated” in that I’m using chan_sip rather than chan_pjsip?

I can’t get my trunk connection to work with chan_pjsip … is the reason.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.