Depending on the carriers switch choice its been noted in the past that some times the switch on the carrier side can have a stale state.. ie a b-channel still gets reported as in use when its not, thus giving you diminished capacity on your pri. Resetting your b-channels clears the channel issue state on the carrier end. you should have something like 86400 as an interval and not hourly. n\ufortunatly I dont have too much information on what carrier class switches tend to have issues with the frequent b-channel resets. If anyone has any more information on this lets toss it on the voip wiki. Phil
________________________________ From: David Cook [mailto:[EMAIL PROTECTED] Sent: Wed 2/20/2008 5:19 PM To: Philip Mullis; 'TAUG' Subject: RE: [on-asterisk] What causes the B's to restart periodically? My config is pretty vanilla so I didn't bother, but after you mentioning zapata I found this on voip-info. Looks like it will do this automatically every 3600 seconds (hourly) if not told otherwise. resetinterval: sets the time in seconds between restart of unused channels, defaults to 3600 minimum 60 seconds. Some PBXs don't like channel restarts. so set the interval to a very long interval e.g. 100000000 or 'never' to disable *entirely*. Thanks. Second part. The D channel should provide heartbeat-type info so does anyone know why we would restart them periodically? - dbc. show us your configs :) There is an option in zapata.conf that will reset b channels -----Original Message----- From: David Cook [mailto:[EMAIL PROTECTED] Sent: Wed 2/20/2008 4:29 PM To: 'TAUG' Subject: [on-asterisk] What causes the B's to restart periodically? Anyone know why the B channels on a PRI periodically restart? Is it Asterisk requesting them to restart or is this the remote end doing this and why does it happen? It always knows to leave alone the channels that are active - good thing!! - but I've never known what is the cause or rationale behind this. -- B-channel 0/5 successfully restarted on span 1
