On Wed, Oct 23, 2013 at 11:27 AM, Salaheddine Elharit < salah.elharit...@gmail.com> wrote:
> hi > > the issue has been solved after change the span from span =1,1,0,ccs,hdb3 > to span =1,0,0,ccs,hdb3 > thanks for everyone > Salaheddine, Just a comment here: I'm not sure who your spans are connected to but, it is highly unlikely that this changed is what fixed your problem. I think it's more likely that the process of reloading something else actually fixed it. What you are doing here is telling span 1 to provide (or ignore) timing to the other end. If it's the case that you're connected to a public e1 pri provider, this probably isn't the correct configuration and will likely cause further problems like slips and alarms. If it's connected to something internal to your business, (like a channel bank), then it's fine. -- Russ Meyerriecks Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA direct: +1 256-428-6025 Check us out at: www.digium.com & www.asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
