Geoff Manning
2006-Apr-27 08:03 UTC
[Asterisk-Users] Slip/Frame Error between Mitel SX-200 and Asterisk
I have a Dell PE SC420 (a no-no with a TE110P) connected to a Mitel SC-200. The Mitel gets Slip and Frame errors that cause the T1 card in the Mitel to go offline and this causes a service interruption. Could the SC-420/TE110P be causing these errors? I know it is listed on the incompatibility list, but do not know what side-effects are caused. Is this one of them???? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060427/b58c1722/attachment.htm
Geoff Manning
2006-Apr-28 11:04 UTC
[Asterisk-Users] Re: Slip/Frame Error between Mitel SX-200 and Asterisk
Skipped content of type multipart/alternative-------------- next part -------------- *****ASTERISK INFO****** bocav01:~# more /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 - SPAN not used as timing source # 1 - SPAN is the primary timing source # 2 - SPAN is the Secondary timing source #span=1,1,0,d4,ami span=1,1,0,d4,b8zs e&m=1-24 ======================== bocav01:~# more /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=no 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 echocancel=no ; ; 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 ;#include "zapata-channels.conf" ;; RXGAIN Caller Side hears softer/louder audio, Tech side reports a bit of choppiness the louder we make it ;; TXGAIN Tech side must hear softer/louder audio although: ;; txgain > 30 causes a no-service ;; txgain < 0 causes call not to go through ;; ;; Fixed clicking/chirping with these setting below ;rxgain=10 ;txgain=15 ; good RX setting. Techs reported choppy audio slightly above and below this value ; Might be able to tweak the RX by decimal up and down rxgain=3 txgain=1 wink=200 ; default 150 debounce=100 ; default 600 flash=300 ; default 300 ;rxwink=5000 ; default 300 ;emdigitwait=500 ; default 500 ;prewink=800 ; default 50 ;preflash=50 ; default 50 ;rxflash=1250 ; default 1250 ;start=1500 ; default 1500 signalling=em_w context=gv-incoming group = 1 channel => 1-17 signalling=em_w context=zap-incoming group = 2 channel => 18-24 ======================== bocav01:~# tail /var/log/asterisk/messages Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 1: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 2: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 3: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 4: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 5: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 6: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 7: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 8: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 9: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 10: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 11: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 12: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 13: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 14: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 15: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 16: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 17: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 18: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 19: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 20: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 21: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 22: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 23: Yellow Alarm Apr 28 08:29:44 WARNING[3837] chan_zap.c: Detected alarm on channel 24: Yellow Alarm Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 1 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 2 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 3 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 4 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 5 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 6 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 7 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 8 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 9 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 10 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 11 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 12 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 13 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 14 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 15 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 16 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 17 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 18 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 19 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 20 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 21 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 22 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 23 Apr 28 09:05:21 NOTICE[3837] chan_zap.c: Alarm cleared on channel 24 *****MITEL INFO****** FORM 42 ?????????????????????????????????????????????????????????????????????????????? ? [ LINK DESCRIPTOR NUMBER : 2 ] OUTGOING ? VALUE ? ??????????????????????????????????????????????????????????????????????????????>? Alarm debounce timer ( 300 - 3200 ms ) ? 2500 ?<? Line Coding ( AMI, AMI&ZCS, B8ZS) ? B8ZS ? ? Line Build Out ( 0, -7.5, -15, -22.5 DB) ? 0 DB ? ? Line Length ( max 132, 265, 398, 533 or 655) ? 0-132 ? ? Framing ( D4 or ESF ) ? D4 ? ? Slip rate - maintenance limit ( 0 - 9000 ) /24 hrs ? 9000 ? ? Slip rate - service limit ( 0 - 9000 ) /24 hrs ? 9000 ? ? Slip rate - network sync limit ( 0 - 9000 ) /24 hrs ? 9000 ? ? BER - maintenance limit ( 10**-n , n = ( 3,4,5,6 )) / hour ? 3 ? ? BER - service limit ( 10**-n , n = ( 3,4,5,6 )) / hour ? 3 ? ? Framing losses - maintenance limit ( 0 - 9000 ) /24 hrs ? 9000 ? ? Framing losses - service limit ( 0 - 9000 ) /24 hrs ? 9000 ? ? RTS timer - service limit exceeded ( 1 - 255 min ) ? 90 ? ? RTS timer - net slip limit exceeded ( 1 - 255 min ) ? 90 ?>? RTS timer - after alarm ( 0 - 300 sec ) ? 10 ?======================== FORM 13 ?????????????????????????????????????????????????????????????????????????????? ? [ T1 E&M TRUNK: 3 ] OPTION NAME [SUPERVISION PARAMETER ] ? STATUS ? ??????????????????????????????????????????????????????????????????????????????>? Reverse to Idle ? NO ?<? Far-end gives answer supervision ? NO ? ? Inhibit automatic supervision ? NO ? ? No seize alarm ? NO ? ? No release alarm ? NO ? ? Toll office ? NO ? ? Is this a CO ? NO ? ? DTMF ? YES ? ? Save Busy-Out Status ? NO ? ? Disconnect timer 150 - 900 ms ( 50 ms inc ) ? 300 ? ? Release acknowledge timer 2 - 240 s ( 2 s inc ) ? 40 ? ? Guard timer 200 - 1000 ms ( 100 ms inc ) ? 800 ? ? Incoming start type ? WINK ? ? Debounce timer 20 - 150 ms ( 10 ms inc ) ? 100 ? ? Wink timer 150 - 300 ms ( 50 ms inc ) ? 200 ? ? Outgoing start type ? WINK ? ? Digit outpulsing ratio ? 60/40 ? ? Outpulse delay timer 100 - 2000 ms ( 100 ms inc ) ? 800 ? ? Flash timer 200 - 700 ms ( 100 ms inc ) ? 300 ?>? Flash type ?LOOP FSH ?<? Flash over trunk ? NO ? ? Interdigit timer 300 - 800 ms ( 100 ms inc ) ? 800 ? ? Wait for delay timer 300 - 5000 ms ( 100 ms inc ) ? 5000 ? ? Remote end is a satellite ? NO ? ? Remote end is a satellite with OPS lines ? NO ? ? Direct access on CO Line Keys: bypass Key System Toll Control ? NO ? ? Release Link Trunk ? NO ?>? QSIG Supplementary Services ? NO ?======================== Do we need to set this in FORM 14 (Non Dial In Trunk) or FORM 15 (Dial in Trunk). It is currently set in FORM 15. ======================== FORM 43 ?????????????????????????????????????????????????????????????????????????????? ? TRUNK TYPE ? BAY ? SLOT ? LINK DESC NUM ? COMMENTS ? ??????????????????????????????????????????????????????????????????????????????>? ? 01 ? 05 ? ? ?<? ? 01 ? 06 ? 01 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ======================== FORM 44 ?????????????????????????????????????????????????????????????????????????????? ? DESCRIPTION ? BAY ? SLOT ? CCT ? COMMENTS ? ??????????????????????????????????????????????????????????????????????????????>? First clock source ? 1 ? 06 ? -- ? ?<? Second clock source ? ? ? ? ? ? Third clock source ? ? ? ? ? ? Fourth clock source ? ? ? ? ? ? Fifth clock source ? ? ? ? ? ? Sixth clock source ? ? ? ? ? ? Seventh clock source ? ? ? ? ? ? Eighth clock source ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ======================== ALARM LEVELS 10:48 AM 28-APR-06 alarm status = NO ALARM ?????????????????????????????????????????????????????????????????????????????? ? PLID ? HOUR ? SLIPS ? FRAME ? BIPOLAR ? STATUS ? STATE ? ?????????????????????????????????????????????????????????????????????????????? ? 1 5 0 0 ? 0 ? 525 ? 938 ? 0 ? ? ? ? 1 5 0 0 ? 1 ? 595 ? 773 ? 0 ? ? ? ? 1 5 0 0 ? 2 ? 548 ? 1230 ? 0 ? ? ? ? 1 5 0 0 ? 3 ? 453 ? 1070 ? 0 ? ? ? ? 1 5 0 0 ? 4 ? 399 ? 371 ? 0 ? ? ? ? 1 5 0 0 ? 5 ? 628 ? 499 ? 0 ? ? ? ? 1 5 0 0 ? 6 ? 560 ? 946 ? 0 ? ? ? ? 1 5 0 0 ? 7 ? 464 ? 732 ? 0 ? ? ? ? 1 5 0 0 ? 8 ? 412 ? 1000 ? 0 ? ? ? ? 1 5 0 0 ? 9 ? 540 ? 914 ? 0 ? ? ? ? 1 5 0 0 ? 10 ? 266 ? 415 ? 0 ? clear ? active ? ? 1 5 0 0 ? 11 ? 0 ? 0 ? 0 ? ? ? ======================== LOGS 10:51 AM 28-APR-06 alarm status = NO ALARM ?????????????????????????????????????????????????????????????????????????????? ? SX-200 LW19 Q45.0.4 23-AUG-2005 Logs ? ?????????????????????????????????????????????????????????????????????????????? ?READ LOGS ALL ? ? ? ?2006-APR-28 09:57:34 T1/BRI card at 01 05 00 00 ? ? has exceeded the maint loss frame threshold ? ? ? ?2006-APR-28 09:57:34 T1/BRI card at 01 05 00 00 ? ? has exceeded the maintenance slip threshold ? ? ? ?2006-APR-28 09:29:18 Tot alarm went from MAJOR to No Alarm ? ? Alarm level change due to Bay 01 trunks ? ? ? ?2006-APR-28 09:29:18 T1/BRI card at 01 05 00 00 ? ? alarm condition is now cleared ? ? ? ?2006-APR-28 09:27:31 Tot alarm went from No Alarm to MAJOR ? ? Alarm level change due to Bay 01 trunks ? ? ? ?2006-APR-28 09:27:31 T1/BRI card at 01 05 00 00 ? ? is in red alarm condition due to loss of sync ? ? ? ?2006-APR-28 09:17:45 T1/BRI card at 01 05 00 00 ? ? has exceeded the maint loss frame threshold ? ? ? ?2006-APR-28 09:04:18 Tot alarm went from MAJOR to No Alarm ? ? Alarm level change due to Bay 01 trunks ? ? ? ?2006-APR-28 09:04:18 T1/BRI card at 01 05 00 00 ? ? alarm condition is now cleared ? ? ? ?2006-APR-28 09:03:50 T1/BRI card at 01 05 00 00 ? ? is receiving a yellow alarm ? ? ? ?2006-APR-28 09:03:30 T1/BRI card at 01 05 00 00 ? ? is in red alarm condition due to loss of sync ? ? ? ?2006-APR-28 08:28:31 T1/BRI card at 01 05 00 00 ? ? removed from service & transmitting yellow alarm ? ? ? ?2006-APR-28 08:28:30 Tot alarm went from No Alarm to MAJOR ? ? Alarm level change due to Bay 01 trunks ? ? ? ?2006-APR-28 08:28:30 T1/BRI card at 01 05 00 00 ? ? has exceeded the service loss frame threshold ? ? ? ?2006-APR-27 16:59:07 T1/BRI card at 01 05 00 00 ? ? has exceeded the maint loss frame threshold ? ? ? ?2006-APR-27 15:14:48 T1/BRI card at 01 05 00 00 ? ? has exceeded the maintenance slip threshold ?