[asterisk-dev] DNS & PJSIP

[Eric Wieling]

Making people configure DNS for each application might the start of an exciting new trend in software!   

We could call the "what nutjob thought of THAT feature" feature.

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Olle E. Johansson
Sent: Monday, March 17, 2014 5:47 AM
To: Asterisk Developers Mailing List
Cc: Olle E Johansson
Subject: [asterisk-dev] DNS & PJSIP

Friends,
After a bit of heated discussion I can try to make a conclusion from what I see when the dust settled:

- We are still in control of our own product and make our own decisions about Asterisk architecture. Any arguments like "PJSIP has it so we have to enable it" falls to the ground as not valid and disappear in a cloud of smoke.

- No one has given any reasons why we should be able to configure DNS servers in the PJSIP channel configuration, apart from Jared who wanted to let users shoot themself in the feet. That is not the way I treat my users. I think most of us now agree that we don't want to have that configuration item.

- In the long run, having a DNS resolver embedded in a module is not a good thing. Due to the PJSIP architecture, it's very hard to avoid. I've spoken with several non-asterisk developers using PJSIP that have partly succeeded, but not fully. We need to stress this to pjsip so that they can separate this code in the future.

- Having PJSIP parse /etc/resolv.conf is not a good thing. If that can't be avoided, we need to monitor the file for updates from Asterisk and reconfigure.

Sorry for being a bit provocative, but some responses I got caused me to become upset. I feel very strongly for keeping our architecture in control and following the soul of Asterisk and the environment we run Asterisk in. 

I think that's all I see in the dust on the battleground. Any comments on this?

Cheers,
/O