[asterisk-users] Why does it take at least 4 flipping days before asterisk tries to resolve a provider?
After a reboot, asterisk is usually too much in a hurry to try and resolve my iax/sip providers. Asterisk starts before the internet connection is up and dns is working. Then asterisk just waits, and waits and waits and waits even longer before ever trying to revolve any voip provider again. And all this time calls are flowing out through the very expensive PSTN. And then people say nightly asterisk restarts are not a good idea ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Why does it take at least 4 flipping days before asterisk tries to resolve a provider?
Remco, Asterisk starts before the internet connection is up and dns is working. knip And then people say nightly asterisk restarts are not a good idea Why is your asterisk startup script running before networking has been setup? Asterisk has the same networking dependencies as apache, so I start it around the same time using the same priority as apache and as far as I know networking should work at that time or not at all, not somewhere in between. pebkac? -- Andreas SikkemaBBeyond Software EngineerPlaneetbaan 4 +31 (0)23 70743422132 HZ Hoofddorp ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Why does it take at least 4 flipping days before asterisk tries to resolve a provider?
On Mon, 2006-10-23 at 10:14 +0200, Andreas Sikkema wrote: Why is your asterisk startup script running before networking has been setup? Asterisk has the same networking dependencies as apache, so I start it around the same time using the same priority as apache and as far as I know networking should work at that time or not at all, not somewhere in between. I've seen this type of nonsense with newer versions of Suse. I've never bothered to find out why, just changed the priority manually to make sure it does what _I_ want. -- Dave Cotton [EMAIL PROTECTED] ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Why does it take at least 4 flipping days before asterisk tries to resolve a provider?
On Mon, 23 Oct 2006, Andreas Sikkema wrote: Remco, Asterisk starts before the internet connection is up and dns is working. knip And then people say nightly asterisk restarts are not a good idea Why is your asterisk startup script running before networking has been setup? Asterisk has the same networking dependencies as apache, so I start it around the same time using the same priority as apache and as far as I know networking should work at that time or not at all, not somewhere in between. It is not, asterisk is correctly started after networking services, however it seems that when the box is booting the dns is replying just a split second too late for the taste of asterisk and it seems that asterisk then marks the provider as unavailable. * should never wait that long, the 'load' on the box to resolve maybe a handful of domains is nothing, even if you would be running a Pentium 1 box, and this should not be any reason not to try again every few minutes or so. pebkac? If your view is broad enough all computer / it related trouble could be traced back to that :) ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Why does it take at least 4 flipping days before asterisk tries to resolve a provider?
Remco Barendse wrote: It is not, asterisk is correctly started after networking services, however it seems that when the box is booting the dns is replying just a split second too late for the taste of asterisk and it seems that asterisk then marks the provider as unavailable. * should never wait that long, the 'load' on the box to resolve maybe a handful of domains is nothing, even if you would be running a Pentium 1 box, and this should not be any reason not to try again every few minutes or so. I was under the impression that it only contacted the hosts if it was registering with them, then it would wait until the value passed in registertimeout (sip.conf) and retry again after that time (if it failed). In practise here (and at work) if the machine has problems contacting registration hosts, anyx sip clients connected to the server (even locally) will not register and any fixed sip peer - user pairs that don't require registration will also not work until it can contact the host again. I doubt this is what's supposed to happen, but that's what happens with me (1.2.12.1 and 1.4b2). ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Why does it take at least 4 flipping days before asterisk tries to resolve a provider?
Thomas Kenyon wrote: Remco Barendse wrote: It is not, asterisk is correctly started after networking services, however it seems that when the box is booting the dns is replying just a split second too late for the taste of asterisk and it seems that asterisk then marks the provider as unavailable. * should never wait that long, the 'load' on the box to resolve maybe a handful of domains is nothing, even if you would be running a Pentium 1 box, and this should not be any reason not to try again every few minutes or so. I was under the impression that it only contacted the hosts if it was registering with them, then it would wait until the value passed in registertimeout (sip.conf) and retry again after that time (if it failed). In practise here (and at work) if the machine has problems contacting registration hosts, anyx sip clients connected to the server (even locally) will not register and any fixed sip peer - user pairs that don't require registration will also not work until it can contact the host again. I doubt this is what's supposed to happen, but that's what happens with me (1.2.12.1 and 1.4b2). This is a known issue. See the mailing list archives. Make sure asterisk does not try to resolve using DNS. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
