> > Damon Estep wrote: > > Can anyone suggest any reasons why a zap (PRI) b channel should not be a > > member of multiple zap trunk group definitions? > > > > > > > > For example; > > > > > > > > Group 1 = Channels 1 to 23 > > > > Group 2 = channels 1 to 12 > > > > Group 3 = channels 13 to 23 > > > > > > > > The purpose is to restrict the number of channels a particular > > extensions can use, but use the entire span for other extensions. > > Part of a production /etc/asterisk/zaptel.conf: > > group=1 > channel => 1-6 > group=1,2 > channel => 7-12 > group=0 > channel => 13-16 >
So the correct solution is to define the channel only once, but the group= parameter can contain many groups delimited by a comma, correct? _______________________________________________ --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
