Hi
I want to solve ipaddress with DNS A queries.
There is the problem that ipddress resolution of the DNS is not correct.
Because Ａsterisk is not put sip. before a message of XX.com
I could see in the log that asterisk send A queries without sip.
Is this problem for asterisk configuration or
First of all apologies for not catching up that conversation, I hadn't found
it before. Thanks for the pointer.
I wouldn't recommend using wildcards for this problem because sometimes the
DNS query contains domain names which are valid and might be used for other
actions (such as
On 11/11/2008 10:48 p.m., samuel wrote:
So far I've updated a few machines (1.4.22) and the DNS queries are reduced
to a minimum, at least haven't seen DNS channel queries...
Slightly more useful to me, does anyone know the patch that fixed it, so
I can update machines I don't want to upgrade
2008/11/10 Matt Riddell [EMAIL PROTECTED]
On 11/11/2008 1:34 a.m., samuel wrote:
Folks,
I'm tracing this error and looks like newer 1.4 (1.4.22) does not behave
as
I stated (no DNS for channel domainname) and it must have been solved in
the
way from my versions to the newer.
I'll
On Tuesday 11 November 2008 05:17:30 Matt Riddell wrote:
On 11/11/2008 10:48 p.m., samuel wrote:
So far I've updated a few machines (1.4.22) and the DNS queries are
reduced to a minimum, at least haven't seen DNS channel queries...
Slightly more useful to me, does anyone know the patch that
Matt Riddell schrieb:
All solved by a caching dns server - achieved in debian by:
apt-get install bind9
followed by change nameserver to 127.0.0.1 in resolv.conf
http://lists.digium.com/pipermail/asterisk-users/2008-September/218764.html
Philipp Kempgen
--
On 12/11/2008 6:20 a.m., Tilghman Lesher wrote:
On Tuesday 11 November 2008 05:17:30 Matt Riddell wrote:
On 11/11/2008 10:48 p.m., samuel wrote:
So far I've updated a few machines (1.4.22) and the DNS queries are
reduced to a minimum, at least haven't seen DNS channel queries...
Slightly more
Folks,
I'm tracing this error and looks like newer 1.4 (1.4.22) does not behave as
I stated (no DNS for channel domainname) and it must have been solved in the
way from my versions to the newer.
I'll update to the newer versions and confirm it.
Apologies for the flames :p
Samuel.
2008/11/10
It not only happens on INVITE or BYE but also happens when a 18x is received
(180 Ringing or 183 Session Progess at least) so it's not directly related
where the Dial command is executed in the dialplan, isn't it? It looks more
as a SIP channel internal stuff...
It looks like there is some
On 11/11/2008 1:34 a.m., samuel wrote:
Folks,
I'm tracing this error and looks like newer 1.4 (1.4.22) does not behave as
I stated (no DNS for channel domainname) and it must have been solved in the
way from my versions to the newer.
I'll update to the newer versions and confirm it.
Hi folks,
I've been using * for quite a few years and everyday it surprises me more.
I was recently analysing some captures with ethereal/wireshark and found out
that * was doing DNS A queries for domain names like
channel.mydomain.comwhere channel is the typical string of the
dstchannel or
On Nov 7, 2008, at 8:29 AM, samuel wrote:
Hi folks,
I've been using * for quite a few years and everyday it surprises me
more.
I was recently analysing some captures with ethereal/wireshark and
found out that * was doing DNS A queries for domain names like
channel.mydomain.com
12 matches
Mail list logo
