* You are viewing Posts Tagged ‘default’

doing dnsmgr_lookup

If your CLI is being spammed with : doing dnsmgr_lookup messages:

[Sep 13 08:31:38] > doing dnsmgr_lookup for ‘ssw6.itsp.tld’
[Sep 13 08:31:38] > doing dnsmgr_lookup for ‘ssw6.itsp.tld’
[Sep 13 08:31:47] > doing dnsmgr_lookup for ‘ssw4.itsp.tld’

You can to turn this off by setting a verbosity to less than 4 or or change main/dnsmgr.c and modify the 4 to something more acceptable to you, then recompile and build.

ast_verb(4, "doing dnsmgr_lookup for ‘%s’\n", name);

asterisk-users Digest, Vol 73, Issue 63

> I have 2 FXO channels from which I want to route incoming calls to
> different contexts in extensions.conf. I edited the context entries in
> dahdi-channels.conf and created matching entries in extensions.conf.
> One channel is routed to the new context as I want, but the other
> channel is stuck going to the default “from-pstn” context no matter what
> I do.
>
> Can anyone see what I’ve missed?
>
>>From dahdi-channels.conf:
> ;;; line=”3 WCTDM/4/2 FXSKS”
> signalling=fxs_ks
> callerid=asreceived
> group=0
> context=from-pstn-3
> channel => 3
> callerid=
> group=
> context=default
>
> ;;; line=”4 WCTDM/4/3 FXSKS”
> signalling=fxs_ks
> callerid=asreceived
> group=0
> context=from-pstn-4
> channel => 4
> callerid=
> group=
> context=default
>
You have multiple “context=” lines in your file and the order within the
file is important. “channel =>” should be the last item. So channel 4 is
actually reading the “context=default” line which is 3 lines under
“channel=>3″ in your config file.