As I recall, it's leftover from an ancient bug that has long been solved. You can turn it off in zapata.conf, but it's harmless.
David Cook wrote: > 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 > > -- B-channel 0/6 successfully restarted on span 1 > > -- B-channel 0/7 successfully restarted on span 1 > > -- B-channel 0/8 successfully restarted on span 1 > > -- B-channel 0/9 successfully restarted on span 1 > > -- B-channel 0/10 successfully restarted on span 1 > > -- B-channel 0/11 successfully restarted on span 1 > > -- B-channel 0/12 successfully restarted on span 1 > > -- B-channel 0/13 successfully restarted on span 1 > > -- B-channel 0/14 successfully restarted on span 1 > > -- B-channel 0/15 successfully restarted on span 1 > > -- B-channel 0/16 successfully restarted on span 1 > > -- B-channel 0/17 successfully restarted on span 1 > > -- B-channel 0/18 successfully restarted on span 1 > > -- B-channel 0/19 successfully restarted on span 1 > > -- B-channel 0/20 successfully restarted on span 1 > > -- B-channel 0/21 successfully restarted on span 1 > > > > - dbc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
