There is a CLI command, “dnsmgr refresh”. There is also a status command.
Oh, okay. This is not resolving the issue. dnsmgr status shows
DNS Manager: enabled
Refresh Interval: 300 seconds
Number of entries: 4
and both dnsmgr refresh and dnsmgr reload do not resolve the issue.
But this appears in the logs:
[2021-11-09 20:01:48] DEBUG[28106] dnsmgr.c: Refreshing DNS lookups.
20919[2021-11-09 20:01:48] DEBUG[28106] dnsmgr.c: refreshing '<External IP address of SIP server>'
20920[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: Splitting '<External IP address of SIP server>' into...
20921[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: ...host '<External IP address of SIP server>' and port ''.
20922[2021-11-09 20:01:48] DEBUG[28106] dnsmgr.c: refreshing '<External IP address of SIP server>'
20923[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: Splitting '<External IP address of SIP server>' into...
20924[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: ...host '<External IP address of SIP server>' and port ''.
20925[2021-11-09 20:01:48] DEBUG[28106] dnsmgr.c: refreshing '<External IP address of SIP server>'
20926[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: Splitting '<External IP address of SIP server>' into...
20927[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: ...host '<External IP address of SIP server>' and port ''.
20928[2021-11-09 20:01:48] DEBUG[28106] dnsmgr.c: refreshing '<External IP address of SIP server>'
20929[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: Splitting '<External IP address of SIP server>' into...
20930[2021-11-09 20:01:48] DEBUG[28106] netsock2.c: ...host '<External IP address of SIP server>' and port ''.
Unfortunately it doesn’t tell how it resolves. But all of this seems to be very weird to me. Whatever I try, I cannot make it work without reloading the transports or Asterisk entirely.
That’s the extent of what I can say, it appears to be DNS related from what I can tell.
With all due respect, but I’m not convinced that it is just DNS related as transport via UDP is working.
With the environment you’re in and how it isn’t easily reproduced, maybe so. Based on the available information from my side it looks like DNS. That’s the extent of what I can say at this point. You can file an issue on the issue tracker[1] if you wish, and the current individual doing triage will ask for any additional information they can think of alongside of the log. There is no time frame on when it would get looked into. I don’t think this is some kind of widespread issue.
Anyone else any idea?
Did you file an Asterisk issue?
Do you have any new evidence that would spur fresh ideas?
@billsimon After the last message I got the impression that this would be a waste of time of the Asterisk team. But I filed one now.
My guess would be that there is an issue when it’s checking if the IP address is in the local network or not. But I couldn’t find the time to properly analyze the PJSIP code and I’m also definitely not a professional in that.
The issue is at [ASTERISK-29834] Incorrect IP in contact header when using PJSIP TLS with dynamic IP addresses (intermittently) - Digium/Asterisk JIRA for those keeping track.
Asterisk is an open source project, individuals besides Sangoma do participate and fix things. Just because we have no time frame on when it would get looked into doesn’t mean someone else wouldn’t take an interest, so filing an issue is fine. Making it as easy as possible for those developers to look is also a good idea - which is why I asked for attaching all of the information to the issue.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.