[Asterisk-Users] B-channels resetting every 60 minutes?
Hello, As you can see are pri is being reset every 60 minutes! Is there a way to stop this?? Is it a Zapata configuration problem? We have a * box with a single port T1/pri card installed. Thanks lach Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 4 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 5 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 6 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 7 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 8 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 9 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 10 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 11 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 12 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 13 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 14 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 15 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 16 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 17 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 18 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 19 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 20 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 21 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 22 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 23 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 4 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 5 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 6 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 7 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 8 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 9 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 10 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 11 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 12 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 13 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 14 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 15 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 16 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 17 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 18 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 19 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 20 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 21 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 22 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 23 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 1 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 4 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 5 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 6 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 7 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 8 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 9 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 10 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 11 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 12 successfully restarted on span 1
RE: [Asterisk-Users] B-channels resetting every 60 minutes?
Hello Lach- I think B channel restarting is a normal occurrence, although I thought it was supposed to be more often than once every 60 minutes. The channels are not supposed to be restarted if they show "in use", so this should be a transparent occurrence. Are there any problems that this is causing? Cheers Scott Stingel Scott M. Stingel Emerging Voice Technology Inc. Palo Alto, California and London, England Email: scott "at" evtmedia.com URL:www.evtmedia.com >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of osx >Sent: Wednesday, April 07, 2004 5:47 PM >To: [EMAIL PROTECTED] >Subject: [Asterisk-Users] B-channels resetting every 60 minutes? > >Hello, > >As you can see are pri is being reset every 60 minutes! Is >there a way to >stop this?? Is it a Zapata configuration problem? > >We have a * box with a single port T1/pri card installed. > >Thanks > >lach > >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 2 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 3 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 4 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 5 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 6 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 7 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 8 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 9 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 10 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 11 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 12 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 13 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 14 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 15 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 16 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 17 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 18 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 19 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 20 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 21 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 22 >successfully restarted >on span 1 >Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 23 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 2 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 3 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 4 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 5 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 6 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 7 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 8 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 9 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 10 >successfully restarted >on span 1 >Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 11 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 12 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 13 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 14 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 15 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 16 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 17 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 18 >successfully restarted >on span 1 >Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 19 >successfully restarted >on span 1 >Apr 7 10:00:09 VE
Re: [Asterisk-Users] B-channels resetting every 60 minutes?
osx wrote: Hello, As you can see are pri is being reset every 60 minutes! Is there a way to stop this?? Is it a Zapata configuration problem? We have a * box with a single port T1/pri card installed. This is an expected and desired behavior. Jeremy McNamara ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] B-channels resetting every 60 minutes?
Hi Lach, this looks like normal behaviour to me. Most of the equipment I use issues a restart upon initial physical connection (bad equipment can cause problems when it doesn't do this) and then several times per hour thereafter. Once every hour seems infrequent but I guess that this is down to individual suppliers' interpretation of the specification documents. HTH Darren -- Comgate Telco>Internetmailto:[EMAIL PROTECTED] Behalf Of osx Sent: 07 April 2004 17:47 To: [EMAIL PROTECTED] Subject: [Asterisk-Users] B-channels resetting every 60 minutes? Hello, As you can see are pri is being reset every 60 minutes! Is there a way to stop this?? Is it a Zapata configuration problem? We have a * box with a single port T1/pri card installed. Thanks lach Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 4 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 5 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 6 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 7 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 8 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 9 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 10 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 11 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 12 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 13 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 14 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 15 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 16 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 17 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 18 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 19 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 20 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 21 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 22 successfully restarted on span 1 Apr 7 09:00:07 VERBOSE[114696]: -- B-channel 23 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 4 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 5 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 6 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 7 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 8 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 9 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 10 successfully restarted on span 1 Apr 7 10:00:08 VERBOSE[114696]: -- B-channel 11 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 12 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 13 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 14 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 15 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 16 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 17 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 18 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 19 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 20 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 21 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 22 successfully restarted on span 1 Apr 7 10:00:09 VERBOSE[114696]: -- B-channel 23 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 1 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 2 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 3 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 4 successfully restarted on span 1 Apr 7 11:00:10 VERBOSE[114696]: -- B-channel 5 successfully restarted on span 1 Apr 7 11:00:10 V
Re: [Asterisk-Users] B-channels resetting every 60 minutes?
Hi Jeremy, Thanks for the response. I made a call just before the hourly reset of all the B-channels. And when it came time for the reset, it did all the channels but the one I was using. So this was not our problem :(( We have one other error (twice today) we get "Out of trunk data space on call number , dropping" How do I determine what is causing this error? we have a point-to-point T1 between 2 * boxes, with 3 phone in the remote office. I have no idea how the trunk could be out of space. The end goal is trying to figure why we are dropping calls! THanks for any insight. lach - Original Message - From: "Jeremy McNamara" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 07, 2004 12:54 PM Subject: Re: [Asterisk-Users] B-channels resetting every 60 minutes? > osx wrote: > > >Hello, > > > >As you can see are pri is being reset every 60 minutes! Is there a way to > >stop this?? Is it a Zapata configuration problem? > > > >We have a * box with a single port T1/pri card installed. > > > > > > This is an expected and desired behavior. > > > Jeremy McNamara > > > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] B-channels resetting every 60 minutes?
> We have one other error (twice today) we get "Out of trunk data space on > call number , dropping" > > How do I determine what is causing this error? we have a point-to-point > T1 > between 2 * boxes, with 3 phone in the remote office. I have no idea how > the trunk could be out of space. > > The end goal is trying to figure why we are dropping calls! Are you running IAX between the boxes? Are you running IAX trunking between the boxes? If so.. Do you have trunking configured identically on both ends (trunk=yes in iax.conf)? Do you have a zaptel device (or ztdummy) in both ends? If either of those questions is no, then you'll get the "out of trunk data space" error and drop calls. Make sure both ends are configured the same for trunking and you have a zaptel device or ztdummy. Or just don't use trunking (trunk=no). ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] B-channels resetting every 60 minutes?
I'd like to jump in here because we're also experiencing the out of trunk data problem. So is this the only thing that causes the out of trunk data error? Because we are running iax between the boxes and both boxes have trunk=yes in the iax.conf entries and there is a zaptel device in both. James Sharp wrote: Are you running IAX between the boxes? Are you running IAX trunking between the boxes? If so.. Do you have trunking configured identically on both ends (trunk=yes in iax.conf)? Do you have a zaptel device (or ztdummy) in both ends? If either of those questions is no, then you'll get the "out of trunk data space" error and drop calls. Make sure both ends are configured the same for trunking and you have a zaptel device or ztdummy. Or just don't use trunking (trunk=no). ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
