[Asterisk-Users] Asterisk and Mitel SX 200 Slip and Frame Errors causing Major Ala rms

[Geoff Manning]

We have integrated an Asterisk (TE110P) and a Mitel SX200. We usually get
over  500 frame errors and over a 500 slip errors per hour. When the errors
reach 1000 per hour the Mitel will take it's T1 card offline. At that point
no calls can be routed from the Asterisk server to the Mitel and the TE110P
reports a Yellow alarm.

What can be causing all these Frame and Slip errors? We have been working
with a Mitel tech to get all the configurations correct and we still haven't
been able to resolve the issue.

We are currently connecting via crossover so we'll try a straight through
just for kicks. We have a spare TE110P so we are going to try that. I just
don't know enough about these errors to know what to try next.	

Any other thoughts?????



CONFIG INFO:

I am running "Asterisk CVS-v1-0-10/10/05-15:00:08".


# cat /etc/zaptel.conf
# Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order

# Global data

loadzone        = us
defaultzone     = us

#span =<span num>, <timing>,<line build out>,<framing>,coding>
# timing values can be
# 0 - not used as timing source
# 1 - primary timing source
# 2 - Secondary timing source

span=1,1,0,d4,ami
e&m=1-24


===================================


# cat /etc/asterisk/zapata.conf
;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]
;
; Trunk groups are used for NFAS or GR-303 connections.
;
; Group: Defines a trunk group.
;        group => <trunkgroup>,<dchannel>[,<backup1>...]
;
;        trunkgroup  is the numerical trunk group to create
;        dchannel    is the zap channel which will have the
;                    d-channel for the trunk.
;        backup1     is an optional list of backup d-channels.
;
;trunkgroup => 1,24,48
;
; Spanmap: Associates a span with a trunk group
;        spanmap => <zapspan>,<trunkgroup>[,<logicalspan>]
;
;        zapspan     is the zap span number to associate
;        trunkgroup  is the trunkgroup (specified above) for the mapping
;        logicalspan is the logical span number within the trunk group to
use.
;                    if unspecified, no logical span number is used.
;
;spanmap => 1,1,1
;spanmap => 2,1,2
;spanmap => 3,1,3
;spanmap => 4,1,4

[channels]
;
; Default language
;
;language=en

musiconhold=default

busydetect=1
busycount=7

relaxdtmf=yes
callwaiting=yes
;
; Support Caller*ID on Call Waiting
;
callwaitingcallerid=yes
;
; Support three-way calling
;
threewaycalling=yes
;
; Support flash-hook call transfer (requires three way calling)
;
transfer=yes
;
; Support call forward variable
;
cancallforward=yes
;
; DR: Commented out temporarily
;echocancel=yes
;
; Generally, it is not necessary (and in fact undesirable) to echo cancel
; when the circuit path is entirely TDM.  You may, however, reverse this
; behavior by enabling the echo cancel during pure TDM bridging below.
;
;echocancelwhenbridged=yes

; Logical groups can be assigned to allow outgoing rollover.  Groups
; range from 0 to 31, and multiple groups can be specified.
;
;group=1
; Ring groups (a.k.a. call groups) and pickup groups.  If a phone is ringing
; and it is a member of a group which is one of your pickup groups, then
; you can answer it by picking up and dialing *8#.  For simple offices, just
; make these both the same
;
callgroup=1
pickupgroup=1

;
; Specify whether the channel should be answered immediately or
; if the simple switch should provide dialtone, read digits, etc.
;
immediate=yes
; For fax detection, uncomment one of the following lines.  The default is
*OFF*
;
;faxdetect=both
;faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no


rxgain=0
txgain=0

signalling=em
wink=200
debounce=100
flash=300

;context=zap-incoming
context=gv-incoming
group = 1
channel => 1-17


signalling=em_w
context=zap-incoming
group = 2
channel => 21-24