[Asterisk-Users] Quad PRI Problems
I have been getting quite a bit of PRI Resets using my Quad PRI Digium card. Prior to the resets I am getting similar notices to the following chan_zap.c:7482 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 3 Telco claims the PRI's are fine on their end and that it is my unit. Is this timing? (google somewhat leads to this) I am running 1.08 asterisk zaptel libpri. Any help would be greatly appreciated. ~ron Zaptel.conf span=1,1,0,esf,b8zs # connects to an Adtran FXS TA624 em=1-24 span=2,1,0,esf,b8zs # Connects to Bell Company 1 bchan=25-47 dchan= 48 span=3,1,0,esf,b8zs # Connects to Bell Company #2 bchan=49-71 dchan= 72 span=4,1,0,esf,b8zs # Connects to Brook Trout CArd em=1-4 defaultzone=us loadzone=us [channels] context=from-internal-receiver ; Points to the default context of your extensions.conf language=en faxdetect=none usecallerid=yes callerid=asreceived threewaycalling=yes transfer=yes signalling=featd ; FXS for ringing phones group=0 flash=350 rxwink=300 prewink=20~~ echocancel=no ; You can set this to 32, 64, or 128, tweak to your needs. echocancelwhenbridged=no immediate=no channel = 1-24 signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master switchtype=national pridialplan=unknown echocancel=yes ; You can set this to 32, 64, or 128, tweak to your needs. echocancelwhenbridged=no echotraining=400 ; Asterisk trains to the beginning of the call, number is in milliseconds group=1 context=from-pstn channel = 25-47 ; Set this to 1-15,17-31 for E1 group=2 signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master switchtype=national channel = 49-71 ; Set this to 1-15,17-31 for E1 group=3 signaling=em_w channel = 73-76 oledata.mso Description: Binary data ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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] Quad PRI Problems
You can't put four span in timing, because only one must be like nmaster sincronization. If one of your telco provide time for your card. Put second value in all span to 0. regards, srsergio -Mensaje original- De: Ronald Hartmann [mailto:[EMAIL PROTECTED] Enviado el: martes, 04 de octubre de 2005 14:33 Para: asterisk-users@lists.digium.com Asunto: [Asterisk-Users] Quad PRI Problems I have been getting quite a bit of PRI Resets using my Quad PRI Digium card. Prior to the resets I am getting similar notices to the following chan_zap.c:7482 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 3 Telco claims the PRI's are fine on their end and that it is my unit. Is this timing? (google somewhat leads to this) I am running 1.08 asterisk zaptel libpri. Any help would be greatly appreciated. ~ron Zaptel.conf span=1,1,0,esf,b8zs # connects to an Adtran FXS TA624 em=1-24 span=2,1,0,esf,b8zs # Connects to Bell Company 1 bchan=25-47 dchan= 48 span=3,1,0,esf,b8zs # Connects to Bell Company #2 bchan=49-71 dchan= 72 span=4,1,0,esf,b8zs # Connects to Brook Trout CArd em=1-4 defaultzone=us loadzone=us [channels] context=from-internal-receiver ; Points to the default context of your extensions.conf language=en faxdetect=none usecallerid=yes callerid=asreceived threewaycalling=yes transfer=yes signalling=featd ; FXS for ringing phones group=0 flash=350 rxwink=300 prewink=20~~ echocancel=no ; You can set this to 32, 64, or 128, tweak to your needs. echocancelwhenbridged=no immediate=no channel = 1-24 signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master switchtype=national pridialplan=unknown echocancel=yes ; You can set this to 32, 64, or 128, tweak to your needs. echocancelwhenbridged=no echotraining=400 ; Asterisk trains to the beginning of the call, number is in milliseconds group=1 context=from-pstn channel = 25-47 ; Set this to 1-15,17-31 for E1 group=2 signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master switchtype=national channel = 49-71 ; Set this to 1-15,17-31 for E1 group=3 signaling=em_w channel = 73-76 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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] Quad PRI Problems
On Tuesday 04 October 2005 08:32, Ronald Hartmann wrote: I have been getting quite a bit of PRI Resets using my Quad PRI Digium card. You've got a problematic setup for Digium's Zaptel cards. You're also running an old version of Asterisk. 1.09 is the stable release and 1.2 is the upcoming next stable release. span=1,1,0,esf,b8zs # connects to an Adtran FXS TA624 span=2,1,0,esf,b8zs # Connects to Bell Company 1 span=3,1,0,esf,b8zs # Connects to Bell Company #2 span=4,1,0,esf,b8zs # Connects to Brook Trout CArd First of all you've got all four spans attempting to synchronize with the other side of the respective span. Digium cards cannot do this; all four spans must share one common clock. Seeing as you have two different telcos coming in to this card, it could be difficult to achieve sync, but telcos generally all come back to one common clock anyway so it may work out all right. I'd set span 1, and 4 to a clocking value of '0' which means do not attempt to sync to this span, use the internal clock. Leave span 2 as is, with clocking set to '1', which means this span is my primary sync source. Set span 3 to a clock value of '2', which means this span is my secondary sync source. To summarize the clocking values: 0 = do not attempt to use this span for a clock source. 1 = this is my primary sync source. Synchronize the internal clock to the recovered clock from this span. 2 = this is my secondary sync source. Use this span's recovered clock as a sync source if my primary sync source is down. 3 = this is my tertiary sync source. Use this span's recovered clock as a sync source if my primary and secondary sync sources are down. 4 = ... you get the idea. Basically the setup I suggested for you is to use telco #1 as the primary sync source, and to fall back to telco #2's clock if telco #1's span goes down. I have suggested not attempting to recover clock from the Adtran nor the Brook Trout spans. Good luck. :-) -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
