Darrin Henshaw wrote: > add resetinterval=never in your zaptel.conf, or chan_dahdi.conf > depending on what you are running. zaptel or dahdi.
Can someone confirm when the default was changed from "never" to 3600 seconds? According to the voip-info wiki, "never" has always been the default. I would tend to agree, because I've never seen this behavior on customer systems until recently. http://www.voip-info.org/wiki/view/Asterisk+config+chan_dahdi.conf The current configs/chan_dahdi.conf.sample says the default is 3600. I don't see anything in the 1.4 changelog about this change. I ran across this troubleshooting a PRI issue, and was concerned that this frequent resetting was related to the customer issues. What happens when a call comes in when a reset is in progress? If this condition can't be handled gracefully (i.e. without failing a call), then I would argue the default is not conservative enough. Just want to know the right way to handle this. Chris > On Wed, Jul 8, 2009 at 10:35 AM, Aman Dhally<aman.dha...@live.com> wrote: >> Hi All, >> >> Hope you all are fine and good, Today i have found that Mine all PRI >> Channels are restating after every interval of one hour, and i have search >> and psot on >> fourms and everyone said that this is a normal behaviour. >> If this is a normal behaviour is there is any way to stop it { i still don't >> know what is the reson to restart ever hour } . Because this is listed >> everywhere that this is a normal behaviour, but not one mention {may be i am >> not able to find it is listed some where} why this is nesessary? and if this >> is not nessary how to stop it... >> I think we all already know the message , but posting it for future >> reference.. >> >> Thanks a lot . >> Aman Dhally >> >> ------------------------------------------------------------------------------------------------------ >> ul 8 04:02:03] VERBOSE[9007] logger.c: Asterisk Event Logger restarted >> [Jul 8 04:02:03] VERBOSE[9007] logger.c: Asterisk Queue Logger restarted >> [Jul 8 04:02:03] VERBOSE[9007] logger.c: -- Remote UNIX connection >> disconnected >> [Jul 8 04:51:30] VERBOSE[3300] logger.c: -- B-channel 0/1 successfully >> restarted on span 1 >> [Jul 8 04:51:35] VERBOSE[3300] logger.c: -- B-channel 0/2 successfully >> restarted on span 1 >> [Jul 8 04:51:40] VERBOSE[3300] logger.c: -- B-channel 0/3 successfully >> restarted on span 1 >> [Jul 8 04:51:45] VERBOSE[3300] logger.c: -- B-channel 0/4 successfully >> restarted on span 1 >> [Jul 8 04:51:50] VERBOSE[3300] logger.c: -- B-channel 0/5 successfully >> restarted on span 1 >> [Jul 8 04:51:55] VERBOSE[3300] logger.c: -- B-channel 0/6 successfully >> restarted on span 1 >> [Jul 8 04:52:00] VERBOSE[3300] logger.c: -- B-channel 0/7 successfully >> restarted on span 1 >> [Jul 8 04:52:05] VERBOSE[3300] logger.c: -- B-channel 0/8 successfully >> restarted on span 1 >> [Jul 8 04:52:10] VERBOSE[3300] logger.c: -- B-channel 0/9 successfully >> restarted on span 1 >> [Jul 8 04:52:15] VERBOSE[3300] logger.c: -- B-channel 0/10 successfully >> restarted on span 1 >> [Jul 8 04:52:20] VERBOSE[3300] logger.c: -- B-channel 0/11 successfully >> restarted on span 1 >> [Jul 8 04:52:25] VERBOSE[3300] logger.c: -- B-channel 0/12 successfully >> restarted on span 1 >> [Jul 8 04:52:30] VERBOSE[3300] logger.c: -- B-channel 0/13 successfully >> restarted on span 1 >> [Jul 8 04:52:35] VERBOSE[3300] logger.c: -- B-channel 0/14 successfully >> restarted on span 1 >> [Jul 8 04:52:40] VERBOSE[3300] logger.c: -- B-channel 0/15 successfully >> restarted on span 1 >> [Jul 8 04:52:45] VERBOSE[3300] logger.c: -- B-channel 0/17 successfully >> restarted on span 1 >> [Jul 8 04:52:50] VERBOSE[3300] logger.c: -- B-channel 0/18 successfully >> restarted on span 1 >> [Jul 8 04:52:55] VERBOSE[3300] logger.c: -- B-channel 0/19 successfully >> restarted on span 1 >> [Jul 8 04:53:00] VERBOSE[3300] logger.c: -- B-channel 0/20 successfully >> restarted on span 1 >> [Jul 8 04:53:05] VERBOSE[3300] logger.c: -- B-channel 0/21 successfully >> restarted on span 1 >> [Jul 8 04:53:10] VERBOSE[3300] logger.c: -- B-channel 0/22 successfully >> restarted on span 1 >> [Jul 8 04:53:15] VERBOSE[3300] logger.c: -- B-channel 0/23 successfully >> restarted on span 1 >> [Jul 8 04:53:20] VERBOSE[3300] logger.c: -- B-channel 0/24 successfully >> restarted on span 1 >> [Jul 8 04:53:25] VERBOSE[3300] logger.c: -- B-channel 0/25 successfully >> restarted on span 1 >> [Jul 8 04:53:30] VERBOSE[3300] logger.c: -- B-channel 0/26 successfully >> restarted on span 1 >> [Jul 8 04:53:35] VERBOSE[3300] logger.c: -- B-channel 0/27 successfully >> restarted on span 1 >> [Jul 8 04:53:40] VERBOSE[3300] logger.c: -- B-channel 0/28 successfully >> restarted on span 1 >> [Jul 8 04:53:45] VERBOSE[3300] logger.c: -- B-channel 0/29 successfully >> restarted on span 1 >> [Jul 8 04:53:50] VERBOSE[3300] logger.c: -- B-channel 0/30 successfully >> restarted on span 1 >> [Jul 8 04:53:55] VERBOSE[3300] logger.c: -- B-channel 0/31 successfully >> restarted on span 1 >> ---------------------------------------------------------------------------------------------------------------------------- >> >> ________________________________ >> Get easy photo sharing with Windows LiveT Photos. Drag n' drop >> _______________________________________________ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users