search for: refreshinterv

...9; [Sep 13 08:31:49] > doing dnsmgr_lookup for 'ssw4.itsp.tld' [Sep 13 08:31:49] > doing dnsmgr_lookup for 'ssw4.itsp.tld' How can I turn this off ?! dnsmgr.conf : [general] enable=no ; enable creation of managed DNS lookups ; default is 'no' ;refreshinterval=1200 ; refresh managed DNS lookups every <n> seconds ; default is 300 (5 minutes) Kind regards, Jonas. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100913/012ab888/attachm...

...ddress change of the sip trunk, not of my > asterisk server. You would probably benefit by enabling the DNS Manager to allow for dynamic IP changes: # cat dnsmgr.conf [general] enable=yes ; enable creation of managed DNS lookups ; default is 'no' refreshinterval=180 ; refresh managed DNS lookups every <n> seconds ; default is 300 (5 minutes) > > Kind regards, > Daniel > >> Am 01.04.2015 um 16:40 schrieb Tech Support <asterisk at voipbusiness.us >> <mailto:asterisk at voipbusiness.us>&...

...runk, not of my >>> asterisk server. >> You would probably benefit by enabling the DNS Manager to allow for >> dynamic IP changes: >> >> # cat dnsmgr.conf [general] enable=yes ; enable creation >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 >> minutes) > > Hello Andres, > > I read that same suggestion elsewhere in connection with Deutsche > Telekom, so it seems there's some benefit in it. > > Daniel, did you t...

...> asterisk server. > >> You would probably benefit by enabling the DNS Manager to allow for > >> dynamic IP changes: > >> > >> # cat dnsmgr.conf [general] enable=yes ; enable creation > >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; > >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 > >> minutes) > > > > Hello Andres, > > > > I read that same suggestion elsewhere in connection with Deutsche > > Telekom, so it seems there's some benefit in...

I have a trunk, and its host=dynamic dns. The problem is, when the IP changes the Sip show peers Still show the old IP of the DNS, I have to reload and save the configuration again so that asterisk recognize the new IP of the DNS. Any idea how to automate such a thing? Or how can I keep asterisk to deal with NAMES as NAMES, and IPs as IPs. Let me know. Thanks. -------------- next

Hi everybody, I've got a very strange problem: As far as I remember I didn't change anything on my Asterisk side. I have 2 SIP providers to which I can place outbound calls. Today I noticed that outbound calls to provider "inode" fail (and inbound from this provider too). On the CLI I get every 20 seconds following messages: Nov 9 20:01:07 NOTICE[952]: chan_sip.c:5422

...ess change of the sip trunk, not of my > > asterisk server. > You would probably benefit by enabling the DNS Manager to allow for > dynamic IP changes: > > # cat dnsmgr.conf [general] enable=yes ; enable creation > of managed DNS lookups ; default is 'no' refreshinterval=180 ; > refresh managed DNS lookups every <n> seconds ; default is 300 (5 > minutes) Hello Andres, I read that same suggestion elsewhere in connection with Deutsche Telekom, so it seems there's some benefit in it. Daniel, did you try it out already? Kind regards, Sebastian

Hello, What's dnsmgr ? Anybody could tell mr more? cat /etc/asterisk/dnsmgr.conf [general] ;enable=yes ; enable creation of managed DNS lookups ; default is 'no' ;refreshinterval=1200 ; refresh managed DNS lookups every <n> seconds ; default is 300 (5 minutes)serveur1:~# Harry ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger...

...*CLI> core stop now Beginning asterisk shutdown.... Executing last minute cleanups == Destroying musiconhold processes Asterisk cleanly ending (0). cat dnsmgr.conf [general] enable=no ; enable creation of managed DNS lookups ; default is 'no' ;refreshinterval=1200 ; refresh managed DNS lookups every <n> seconds ; default is 300 (5 minutes)

...> asterisk server. > >> You would probably benefit by enabling the DNS Manager to allow for > >> dynamic IP changes: > >> > >> # cat dnsmgr.conf [general] enable=yes ; enable creation > >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; > >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 > >> minutes) > > > > Hello Andres, > > > > I read that same suggestion elsewhere in connection with Deutsche > > Telekom, so it seems there's some benefit in...

...e web to being able to configure Asterisk with DNS related settings. ("Unless specifically configured, Asterisk 1.2does not honor DNS Time To Live (TTL)." from *http://tinyurl.com/2ossv6) *We've tried doing: [dnsmgr.conf] enable=yes ; enable creation of managed DNS lookups refreshinterval=300 ; refresh managed DNS lookups every <n> seconds But this doesn't work, apparently since chan_sip doesn't use dnsmgr. We figure that many other people must need to have Asterisk process updated DNS info and that we must just be missing some configuration. Is that the case or...

...---------------------- The samba-tool dns zoneoptions command can be used to turn aging on and off, alter the refresh and no-refresh periods, and manipulate the timestamps of existing records. To turn aging on for a zone, you can use something like this: ? samba-tool dns zoneoptions --aging=1 --refreshinterval=306600 which turns on aging and ensures no records less than five years old are aged out and scavenged. After aging has been on for sufficient time for records to be renewed, the command ? samba-tool dns zoneoptions --refreshinterval=168 will set the refresh period to the standard seven days....

...---------------------- The samba-tool dns zoneoptions command can be used to turn aging on and off, alter the refresh and no-refresh periods, and manipulate the timestamps of existing records. To turn aging on for a zone, you can use something like this: ? samba-tool dns zoneoptions --aging=1 --refreshinterval=306600 which turns on aging and ensures no records less than five years old are aged out and scavenged. After aging has been on for sufficient time for records to be renewed, the command ? samba-tool dns zoneoptions --refreshinterval=168 will set the refresh period to the standard seven days....

.... >> >> You would probably benefit by enabling the DNS Manager to allow for >> >> dynamic IP changes: >> >> >> >> # cat dnsmgr.conf [general] enable=yes ; enable creation >> >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; >> >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 >> >> minutes) >> > >> > Hello Andres, >> > >> > I read that same suggestion elsewhere in connection with Deutsche >> > Telekom, so it seems...

.... >> >> You would probably benefit by enabling the DNS Manager to allow for >> >> dynamic IP changes: >> >> >> >> # cat dnsmgr.conf [general] enable=yes ; enable creation >> >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; >> >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 >> >> minutes) >> > >> > Hello Andres, >> > >> > I read that same suggestion elsewhere in connection with Deutsche >> > Telekom, so it seems...

Hi list! Yesterday Deutsche Telekom had a really big problem and Asterisk couldn't connect to the remote Server (by Telekom) until today about 7:30. Well, it could happen... What I find really annoying was that I needed to restart Asterisk as I checked with sipsak that the Telekom-Server works... I think, this should not be normal... Can someone explain me why it happens and what I have to

...gt; You would probably benefit by enabling the DNS Manager to allow for >>> >> dynamic IP changes: >>> >> >>> >> # cat dnsmgr.conf [general] enable=yes ; enable creation >>> >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; >>> >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 >>> >> minutes) >>> > >>> > Hello Andres, >>> > >>> > I read that same suggestion elsewhere in connection with Deutsche >>&g...

If I correctly understand what the problem is, what I did was write a script that runs out of CRON every 15 minutes. It checks the outside IP address by querying http://checkip.dyndns.org and compares it to the IP address stored in the parameter ?externip? in the [general] section of sip.conf. If the two values are the same, the script exits quietly. If they are different, the script updates

...gt; You would probably benefit by enabling the DNS Manager to allow for >>> >> dynamic IP changes: >>> >> >>> >> # cat dnsmgr.conf [general] enable=yes ; enable creation >>> >> of managed DNS lookups ; default is 'no' refreshinterval=180 ; >>> >> refresh managed DNS lookups every <n> seconds ; default is 300 (5 >>> >> minutes) >>> > >>> > Hello Andres, >>> > >>> > I read that same suggestion elsewhere in connection with Deutsche >>&g...