Re: [asterisk-users] Disappearing B-Channels
Tilghman, Could you clarify what you mean when you say you added usleep(1) to the end of the manager thread? I do not have enough experience to follow what you're saying. Are you talking about adding this command to the end of the manager.conffile? - Mark ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
On Tuesday 19 February 2008 22:20:06 Mark Greene wrote: Could you clarify what you mean when you say you added usleep(1) to the end of the manager thread? I do not have enough experience to follow what you're saying. I added the comment about what I did to fix it in the source, for those who can follow. If you can't follow, then don't worry about it. Are you talking about adding this command to the end of the manager.conffile? No. -- Tilghman ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
OK thanks for the effort. What's a way to look for IRQ misses in linux? On Feb 20, 2008 12:33 AM, Tilghman Lesher [EMAIL PROTECTED] wrote: On Tuesday 19 February 2008 22:20:06 Mark Greene wrote: Could you clarify what you mean when you say you added usleep(1) to the end of the manager thread? I do not have enough experience to follow what you're saying. I added the comment about what I did to fix it in the source, for those who can follow. If you can't follow, then don't worry about it. Are you talking about adding this command to the end of the manager.conffile? No. -- Tilghman ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
I could do that. The only issue is that I don't understand why others with my setup have not had to do the same. What's unique about my TDMoE setup that makes it intolerant to channel restarts? I did everything by the book. On Feb 11, 2008 11:06 AM, Jared Smith [EMAIL PROTECTED] wrote: On Sun, 2008-02-10 at 22:01 -0600, Mark Greene wrote: Let's compare. Right now I am restarting asterisk when convenient every hour, and that's keeping the symptoms at bay. Have you tried setting resetinterval=never in zapata.conf? By default, Asterisk resets all *idle* bearer channels (B-channels) every hour. (When you say you're restarting every hour, that gave me the idea that maybe the B-channel restarts have something to do with it.) -- Jared Smith Community Relations Manager Digium, Inc. ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
On Monday 11 February 2008 13:57, Ben Willcox wrote: Mark Greene wrote: I could do that. The only issue is that I don't understand why others with my setup have not had to do the same. What's unique about my TDMoE setup that makes it intolerant to channel restarts? I did everything by the book. We had a similar problem, and although your symptoms are not identical, we had a massive ongoing problem with the reliability of our ISDN channels, where they would randomly stop working until eventually we could no longer make any outgoing or incoming calls via our PRI line. A restart of asterisk was needed to get it working again. We finally discovered that the problem was our use of cacti, monitoring channel usage via the manager interface. We were hitting the manager interface with 4 connects, queries and disonnects per minute, and over the course of a day, asterisk would start dropping calls and other strange behaviour. I guess there is a memory leak or similar with the asterisk manager interface. Perhaps not your particular problem, but thought I'd throw it in there anyway as you never know... We had a problem with the manager interface like this that is now fixed. The issue was that if a thread's lifetime was less than one complete context switch, then the master manager thread would write information to memory that had already been deallocated (and possibly allocated to something else). We fixed this by adding a usleep(1) to the end of the manager thread, which ensures that each manager thread will last at least past the first context switch, which is enough to prevent this memory corruption. Any thread that lasts for shorter than a complete context switch (which is 1/10th of a second since, well, forever) or whenever a thread yields the processor, whichever comes first, could also cause similar memory corruption. -- Tilghman ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
Mark Greene wrote: I could do that. The only issue is that I don't understand why others with my setup have not had to do the same. What's unique about my TDMoE setup that makes it intolerant to channel restarts? I did everything by the book. We had a similar problem, and although your symptoms are not identical, we had a massive ongoing problem with the reliability of our ISDN channels, where they would randomly stop working until eventually we could no longer make any outgoing or incoming calls via our PRI line. A restart of asterisk was needed to get it working again. We finally discovered that the problem was our use of cacti, monitoring channel usage via the manager interface. We were hitting the manager interface with 4 connects, queries and disonnects per minute, and over the course of a day, asterisk would start dropping calls and other strange behaviour. I guess there is a memory leak or similar with the asterisk manager interface. Perhaps not your particular problem, but thought I'd throw it in there anyway as you never know... Cheers, Ben ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
On Sun, 2008-02-10 at 22:01 -0600, Mark Greene wrote: Let's compare. Right now I am restarting asterisk when convenient every hour, and that's keeping the symptoms at bay. Have you tried setting resetinterval=never in zapata.conf? By default, Asterisk resets all *idle* bearer channels (B-channels) every hour. (When you say you're restarting every hour, that gave me the idea that maybe the B-channel restarts have something to do with it.) -- Jared Smith Community Relations Manager Digium, Inc. ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
On Sunday 10 February 2008 01:44:38 Mark Greene wrote: In my efforts to solve a mystery of asterisk slowly loosing it's ability to take incoming and outgoing calls I set asterisk to restart b-channels every 60 seconds hoping I would find something odd after some time. So now I am looking at the CLI a few hours later and look what happens when asterisk restarts the 23 b-channels I have. pbx1*CLI -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 == Primary D-Channel on span 1 down [Feb 10 01:41:23] WARNING[4102]: chan_zap.c:2401 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway! [Feb 10 01:41:24] ERROR[4102]: chan_zap.c:8200 zt_pri_error: !! Got S-frame while link down == Primary D-Channel on span 1 up -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 -- B-channel 0/23 successfully restarted on span 1 pbx1*CLI That's the output while I've been writing this email. Those are TWO restarts of the b-channels. Notice I am missing a seizable amount of my 23 b-channels. Where are they going?! How do I find out? I've recompiled my asterisk, zaptel, and libpri to the most recent versions but that's made no difference. You probably have noise on your T1 circuit, which is causing the PRI signalling to become corrupt. If this continues, expect that the T1 circuit will go down from time to time, for a few seconds each time. Your solution is to call your telco and ask for a loopback test. -- Tilghman ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
I don't think it's my telco, I think it's my TDMoE setup. Does that sound possible? I've never had problems with the circuit until I moved it from a standard digium PRI card to a TDMoE device. Also, if I restart asterisk, all the b-channels come back. Thoughts? On Feb 10, 2008 9:40 AM, Tilghman Lesher [EMAIL PROTECTED] wrote: On Sunday 10 February 2008 01:44:38 Mark Greene wrote: In my efforts to solve a mystery of asterisk slowly loosing it's ability to take incoming and outgoing calls I set asterisk to restart b-channels every 60 seconds hoping I would find something odd after some time. So now I am looking at the CLI a few hours later and look what happens when asterisk restarts the 23 b-channels I have. pbx1*CLI -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 == Primary D-Channel on span 1 down [Feb 10 01:41:23] WARNING[4102]: chan_zap.c:2401 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway! [Feb 10 01:41:24] ERROR[4102]: chan_zap.c:8200 zt_pri_error: !! Got S-frame while link down == Primary D-Channel on span 1 up -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 -- B-channel 0/23 successfully restarted on span 1 pbx1*CLI That's the output while I've been writing this email. Those are TWO restarts of the b-channels. Notice I am missing a seizable amount of my 23 b-channels. Where are they going?! How do I find out? I've recompiled my asterisk, zaptel, and libpri to the most recent versions but that's made no difference. You probably have noise on your T1 circuit, which is causing the PRI signalling to become corrupt. If this continues, expect that the T1 circuit will go down from time to time, for a few seconds each time. Your solution is to call your telco and ask for a loopback test. -- Tilghman ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
Mark, I thought I would also mention that I am still having similar issues even after updating to the latest Asterisk, Zaptel and Libpri. Although I am using a Sangoma, we have similar symptoms with a restart fixing it. I am starting to wonder if I must go back to a Digium card. We originally switched away from the Digium TE110 because of interrupt issues, I think that the interrupt issue has been remedied now. _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Greene Sent: Sunday, February 10, 2008 11:15 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Disappearing B-Channels I don't think it's my telco, I think it's my TDMoE setup. Does that sound possible? I've never had problems with the circuit until I moved it from a standard digium PRI card to a TDMoE device. Also, if I restart asterisk, all the b-channels come back. Thoughts? On Feb 10, 2008 9:40 AM, Tilghman Lesher [EMAIL PROTECTED] wrote: On Sunday 10 February 2008 01:44:38 Mark Greene wrote: In my efforts to solve a mystery of asterisk slowly loosing it's ability to take incoming and outgoing calls I set asterisk to restart b-channels every 60 seconds hoping I would find something odd after some time. So now I am looking at the CLI a few hours later and look what happens when asterisk restarts the 23 b-channels I have. pbx1*CLI -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 == Primary D-Channel on span 1 down [Feb 10 01:41:23] WARNING[4102]: chan_zap.c:2401 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway! [Feb 10 01:41:24] ERROR[4102]: chan_zap.c:8200 zt_pri_error: !! Got S-frame while link down == Primary D-Channel on span 1 up -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 -- B-channel 0/23 successfully restarted on span 1 pbx1*CLI That's the output while I've been writing this email. Those are TWO restarts of the b-channels. Notice I am missing a seizable amount of my 23 b-channels. Where are they going?! How do I find out? I've recompiled my asterisk, zaptel, and libpri to the most recent versions but that's made no difference. You probably have noise on your T1 circuit, which is causing the PRI signalling to become corrupt. If this continues, expect that the T1 circuit will go down from time to time, for a few seconds each time. Your solution is to call your telco and ask for a loopback test. -- Tilghman ___ -- 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 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.20.0/1268 - Release Date: 2/9/2008 11:54 AM ___ -- 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
Re: [asterisk-users] Disappearing B-Channels
Kevin, Let's compare. Right now I am restarting asterisk when convenient every hour, and that's keeping the symptoms at bay. However if I let the problem get to the point that it won't take ANY incoming / outgoing calls then I cannot even initiate a restart from the CLI. I have to back all the way out of the CLI to the system prompt and actually call the init script to restart the asterisk service itself. Is this similar for you? What is your system? I am running Dell Poweredge P4 2.8 Ghz 512 MB RAM 80 GB HDD on Software RAID 1 CentOS 5 Kernel 2.6.18-53.1.4.el5 i686 Asterisk 1.4.18 Zaptel 1.4.8 Libpri 1.4.3 asterisk-addons 1.4.5 On Feb 10, 2008 5:06 PM, Kevin Kiely [EMAIL PROTECTED] wrote: Mark, I thought I would also mention that I am still having similar issues even after updating to the latest Asterisk, Zaptel and Libpri. Although I am using a Sangoma, we have similar symptoms with a restart fixing it. I am starting to wonder if I must go back to a Digium card. We originally switched away from the Digium TE110 because of interrupt issues, I think that the interrupt issue has been remedied now. -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Mark Greene *Sent:* Sunday, February 10, 2008 11:15 AM *To:* Asterisk Users Mailing List - Non-Commercial Discussion *Subject:* Re: [asterisk-users] Disappearing B-Channels I don't think it's my telco, I think it's my TDMoE setup. Does that sound possible? I've never had problems with the circuit until I moved it from a standard digium PRI card to a TDMoE device. Also, if I restart asterisk, all the b-channels come back. Thoughts? On Feb 10, 2008 9:40 AM, Tilghman Lesher [EMAIL PROTECTED] wrote: On Sunday 10 February 2008 01:44:38 Mark Greene wrote: In my efforts to solve a mystery of asterisk slowly loosing it's ability to take incoming and outgoing calls I set asterisk to restart b-channels every 60 seconds hoping I would find something odd after some time. So now I am looking at the CLI a few hours later and look what happens when asterisk restarts the 23 b-channels I have. pbx1*CLI -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 == Primary D-Channel on span 1 down [Feb 10 01:41:23] WARNING[4102]: chan_zap.c:2401 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway! [Feb 10 01:41:24] ERROR[4102]: chan_zap.c:8200 zt_pri_error: !! Got S-frame while link down == Primary D-Channel on span 1 up -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 -- B-channel 0/23 successfully restarted on span 1 pbx1*CLI That's the output while I've been writing this email. Those are TWO restarts of the b-channels. Notice I am missing a seizable amount of my 23 b-channels. Where are they going?! How do I find out? I've recompiled my asterisk, zaptel, and libpri to the most recent versions but that's made no difference. You probably have noise on your T1 circuit, which is causing the PRI signalling to become corrupt. If this continues, expect that the T1 circuit will go down from time to time, for a few seconds each time. Your solution is to call your telco and ask for a loopback test. -- Tilghman ___ -- 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 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.20.0/1268 - Release Date: 2/9/2008 11:54 AM ___ -- 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
[asterisk-users] Disappearing B-Channels
In my efforts to solve a mystery of asterisk slowly loosing it's ability to take incoming and outgoing calls I set asterisk to restart b-channels every 60 seconds hoping I would find something odd after some time. So now I am looking at the CLI a few hours later and look what happens when asterisk restarts the 23 b-channels I have. pbx1*CLI -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 == Primary D-Channel on span 1 down [Feb 10 01:41:23] WARNING[4102]: chan_zap.c:2401 pri_find_dchan: No D-channels available! Using Primary channel 24 as D-channel anyway! [Feb 10 01:41:24] ERROR[4102]: chan_zap.c:8200 zt_pri_error: !! Got S-frame while link down == Primary D-Channel on span 1 up -- B-channel 0/19 successfully restarted on span 1 -- B-channel 0/21 successfully restarted on span 1 -- B-channel 0/23 successfully restarted on span 1 pbx1*CLI That's the output while I've been writing this email. Those are TWO restarts of the b-channels. Notice I am missing a seizable amount of my 23 b-channels. Where are they going?! How do I find out? I've recompiled my asterisk, zaptel, and libpri to the most recent versions but that's made no difference. - Mark ___ -- 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
