Hi, I have a client who has a system with a Sangoma 1 port PRI card with echo canceling in it. For some reason, when the system comes up the PRI will stay up for about 4-5 hours, then drop. "zap show status" shows everything as ok, but we can't make or receive any calls until the system is rebooted. Just restarting asterisk does not fix the problem. I am going to call Verizon, however wanted to consult the list to see if anyone here had any ideas. At this point, I am putting my finger on a Verizon issue, as in our lab the system did not have any issues keeping the PRI active and taking calls. Any thoughts?
Matt wrote:> Hi, > I have a client who has a system with a Sangoma 1 port PRI card with > echo canceling in it. For some reason, when the system comes up the > PRI will stay up for about 4-5 hours, then drop. "zap show status" > shows everything as ok, but we can't make or receive any calls until > the system is rebooted. Just restarting asterisk does not fix the > problem. > > I am going to call Verizon, however wanted to consult the list to see > if anyone here had any ideas. At this point, I am putting my finger > on a Verizon issue, as in our lab the system did not have any issues > keeping the PRI active and taking calls. > > Any thoughts? >Generally I have more meaningful conversations with my dog than with Verizon, but I would also involve Sangoma just to be sure it isn't some obscure issue with the card or driver. Sangoma has excellent support, and should be the first contact. John Novack -- Dog is my co-pilot
I have verified it is EXACTLY 5 hours. At 5 hours, the PRI stops working until I issue a restart on the wanrouter interface. I have a call into Sangoma and Verizon to figure out who's problem it is. Can anyone offer any thoughts? On 8/5/07, Matt <mhoppes at gmail.com> wrote:> Hi, > I have a client who has a system with a Sangoma 1 port PRI card with > echo canceling in it. For some reason, when the system comes up the > PRI will stay up for about 4-5 hours, then drop. "zap show status" > shows everything as ok, but we can't make or receive any calls until > the system is rebooted. Just restarting asterisk does not fix the > problem. > > I am going to call Verizon, however wanted to consult the list to see > if anyone here had any ideas. At this point, I am putting my finger > on a Verizon issue, as in our lab the system did not have any issues > keeping the PRI active and taking calls. > > Any thoughts? >
Stephen Bosch wrote:> Steve Totaro wrote: > >> Note to Digium >> >> I wish I could upgrade my wct4xxp drivers locally. I still have the v1 >> firmware on my card. >> >> It is kind of hard (next to impossible) to pull it from a production >> machine and ship it to Digium. That might take a week if all goes well. >> > > The only way this will ever happen is if Digium completely redesigns the > card, which is a long way of saying that you will buy a new card before > you have that request filled. > > This is one of the great things about the Sangoma hardware -- it was > designed to be fully "field upgradeable" (they use an FPGA > architecture). The design approach is worth emulating. > > -Stephen- > >I will go Sangoma from now on with maybe a few test systems running the Tormenta III boards which can be had for under $500 for four ports. They also fit 3.3v and 5v. Thanks, Steve Totaro
Sangoma is working on it with me.... just for information here is what appears in /var/log/messages when the PRI goes down: Aug 7 06:11:48 EMSPBX kernel: wanpipe1: Critical: Echo Canceller Chip Security Compromised: Disabling Driver! Aug 7 06:11:48 EMSPBX kernel: wanpipe1: Please call Sangoma Tech Support (www.sangoma.com)! Aug 7 06:11:48 EMSPBX kernel: wanpipe1: Error: Card Critically Shutdown! Aug 7 06:11:48 EMSPBX kernel: wanpipe1: T1 Front End unconfigation! Aug 7 06:11:48 EMSPBX kernel: wanpipe1: AFT communications disabled! On 8/5/07, Matt <mhoppes at gmail.com> wrote:> Hi, > I have a client who has a system with a Sangoma 1 port PRI card with > echo canceling in it. For some reason, when the system comes up the > PRI will stay up for about 4-5 hours, then drop. "zap show status" > shows everything as ok, but we can't make or receive any calls until > the system is rebooted. Just restarting asterisk does not fix the > problem. > > I am going to call Verizon, however wanted to consult the list to see > if anyone here had any ideas. At this point, I am putting my finger > on a Verizon issue, as in our lab the system did not have any issues > keeping the PRI active and taking calls. > > Any thoughts? >