[Home]

Summary:ASTERISK-11329: Problem connecting Asterisk to UMC-1000 using GR-303
Reporter:Perry Browning (perryb)Labels:
Date Opened:2008-01-29 14:06:22.000-0600Date Closed:2008-02-01 15:14:38.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/Channels
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Description: I can not establish GR-303 connectivity between Asterisk and AFC/Tellabs UMC-1000 digital loop carrier. Asterisk indicates that the TMC is up immediately after initialization; however the UMC shows both the TMC and EOC in a “down” state. I can not find any data related to the state of the EOC in Asterisk.

I have attached what I feel is pertinent data from both the UMC and Asterisk. If additional information is required, please let me know, and I will provide ASAP.

BTW, there's not a lot of onformation on this subject. That said, I noticed references to GR-303 EOC and TMC switch types (8 and 9 respectively) in libpri.h along with other switch types as defined in Zapata.conf. Is there a switch type for GR-303 similar to dms100 or 5ess in zapata.conf or is the datafill in zaptel.conf and zapata.conf as provided in the additional information section below sufficient?

****** ADDITIONAL INFORMATION ******

***** UMC-1000 Info *****

List GR-303 Group

Switch Type:                  DMS
Forward Alarms To Switch:     GR-303
Report TID in Alarm Strings:  No

LET GR303 Group 3


Entity      Location    Status         Entity      Location     Status
-------------------------------------------------------------------------------
DLPA        LET-1-12    Active         DLPB        None                      

EOCA        LET-2-22-12 Down           EOCB        None                      
TMCA        LET-2-22-24 Down           TMCB        None                      

DS1 1   Pri LET-2-22    In-Service     DS1 15      None                      
DS1 2   Sec None                       DS1 16      None                      
DS1 3       None                       DS1 17      None                      
DS1 4       None                       DS1 18      None                      
DS1 5       None                       DS1 19      None                      
DS1 6       None                       DS1 20      None                      
DS1 7       None                       DS1 21      None                      
DS1 8       None                       DS1 22      None                      
DS1 9       None                       DS1 23      None                      
DS1 10      None                       DS1 24      None                      
DS1 11      None                       DS1 25      None                      
DS1 12      None                       DS1 26      None                      
DS1 13      None                       DS1 27      None                      
DS1 14      None                       DS1 28      None                      

Group 3 Listed


List GR-303 Data Link Parameters

Layer 2 Parameters                                     SAPI0       SAPI1
-------------------------------------------------------------------------------

   T200 - Acknowledge Timer                   :   150 mSeconds   150 mSeconds
   N200 - Number of Retransmissions           :     3 Retries      3 Retries
   T203 - Activity Timer                      :    30 Seconds     30 Seconds
   MaxIFrame - Unacknowledged Frames          :     7 Frames       7 Frames  

Layer 3 Timers
-------------------------------------------------------------------------------
   T303 - Timer for SETUP reply               :   700  mSeconds
   T308 - Timer for RELEASE reply             :     4  Seconds
   T396 - 2nd Timer for SETUP reply           : 14700  mSeconds
   T397 - Timer for INFORMATION acknowledge   :   120  Seconds

GR-303 Group 3 Data Link Listed



***** Asterisk Snippets *****

++++ zaptel.conf +++++

# Span 1: WCT1/0 "Digium Wildcard TE120P T1/E1 Card 0" B8ZS/ESF

span=1,3,1,esf,b8zs
fxoks=1-11
dchan=12
fxoks=13-23
dchan=24


++++ zapata.conf ++++

trunkgroup => 3,24
spanmap => 1,3,1

signalling=gr303fxoks_net
channel => 1-11,13-23

signalling=fxo_ks
crv => 3:1-11,13-23


***** Asterisk Start Snippets *****

== Parsing '/etc/asterisk/zapata.conf': Found
 == Created trunk group 3 with Primary D-channel 24 and 0 backup
 == Mapped span 1 to trunk group 3 (logical span 1)
   -- Registered channel 1, GR-303 with FXOKS signalling
   -- Registered channel 2, GR-303 with FXOKS signalling
   -- Registered channel 3, GR-303 with FXOKS signalling
   -- Registered channel 4, GR-303 with FXOKS signalling
   -- Registered channel 5, GR-303 with FXOKS signalling
   -- Registered channel 6, GR-303 with FXOKS signalling
   -- Registered channel 7, GR-303 with FXOKS signalling
   -- Registered channel 8, GR-303 with FXOKS signalling
   -- Registered channel 9, GR-303 with FXOKS signalling
   -- Registered channel 10, GR-303 with FXOKS signalling
   -- Registered channel 11, GR-303 with FXOKS signalling
   -- Registered channel 13, GR-303 with FXOKS signalling
   -- Registered channel 14, GR-303 with FXOKS signalling
   -- Registered channel 15, GR-303 with FXOKS signalling
   -- Registered channel 16, GR-303 with FXOKS signalling
   -- Registered channel 17, GR-303 with FXOKS signalling
   -- Registered channel 18, GR-303 with FXOKS signalling
   -- Registered channel 19, GR-303 with FXOKS signalling
   -- Registered channel 20, GR-303 with FXOKS signalling
   -- Registered channel 21, GR-303 with FXOKS signalling
   -- Registered channel 22, GR-303 with FXOKS signalling
   -- Registered channel 23, GR-303 with FXOKS signalling
   -- Registered CRV 3:1, FXO Kewlstart signalling
   -- Registered CRV 3:2, FXO Kewlstart signalling
   -- Registered CRV 3:3, FXO Kewlstart signalling
   -- Registered CRV 3:4, FXO Kewlstart signalling
   -- Registered CRV 3:5, FXO Kewlstart signalling
   -- Registered CRV 3:6, FXO Kewlstart signalling
   -- Registered CRV 3:7, FXO Kewlstart signalling
   -- Registered CRV 3:8, FXO Kewlstart signalling
   -- Registered CRV 3:9, FXO Kewlstart signalling
   -- Registered CRV 3:10, FXO Kewlstart signalling
   -- Registered CRV 3:11, FXO Kewlstart signalling
   -- Registered CRV 3:13, FXO Kewlstart signalling
   -- Registered CRV 3:14, FXO Kewlstart signalling
   -- Registered CRV 3:15, FXO Kewlstart signalling
   -- Registered CRV 3:16, FXO Kewlstart signalling
   -- Registered CRV 3:17, FXO Kewlstart signalling
   -- Registered CRV 3:18, FXO Kewlstart signalling
   -- Registered CRV 3:19, FXO Kewlstart signalling
   -- Registered CRV 3:20, FXO Kewlstart signalling
   -- Registered CRV 3:21, FXO Kewlstart signalling
   -- Registered CRV 3:22, FXO Kewlstart signalling
   -- Registered CRV 3:23, FXO Kewlstart signalling
   -- Automatically generated pseudo channel

== Starting D-Channel on span 1

Asterisk Ready.
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 1
[Jan 29 09:29:01] NOTICE[5179]: chan_zap.c:8486 pri_dchannel: PRI got event: No more alarm (5) on Primary D-channel of span 1
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 2
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 3
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 4
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 5
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 6
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 7
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 8
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 9
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 10
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 11
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 13
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 14
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 15
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 16
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 17
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 18
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 19
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 20
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 21
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 22
[Jan 29 09:29:01] NOTICE[5180]: chan_zap.c:6678 handle_init_event: Alarm cleared on channel 23
 == Primary D-Channel on span 1 up



***** Asterisk CLI *****

sip-gw2*CLI> pri show span 1
Primary D-channel: 24
Status: Provisioned, Up, Active
Switchtype: GR303 TMC
Type: Network
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 1
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3


sip-gw2*CLI> pri intense debug span 1

> [ 02 01 01 01 ]

> Supervisory frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
-- Restarting T203 counter

< [ 02 01 01 01 ]

< Supervisory frame:
< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1
< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data
-- ACKing all packets from 0 to (but not including) 0
-- Since there was nothing left, stopping T200 counter
-- Stopping T203 counter since we got an ACK
-- Nothing left, starting T203 counter
-- Got RR response to our frame
-- Restarting T203 counter

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
T203 counter expired, sending RR and scheduling T203 again
Sending Receiver Ready (0)

> [ 02 01 01 01 ]

> Supervisory frame:
> SAPI: 00  C/R: 1 EA: 0
>  TEI: 000        EA: 1
> Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
> N(R): 000 P/F: 1
> 0 bytes of data
-- Restarting T203 counter

< [ 02 01 01 01 ]

< Supervisory frame:
< SAPI: 00  C/R: 1 EA: 0
<  TEI: 000        EA: 1
< Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
< N(R): 000 P/F: 1
< 0 bytes of data
-- ACKing all packets from 0 to (but not including) 0
-- Since there was nothing left, stopping T200 counter
-- Stopping T203 counter since we got an ACK
-- Nothing left, starting T203 counter
-- Got RR response to our frame
-- Restarting T203 counter

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data

< [ 04 01 7f ]

< Unnumbered frame:
< SAPI: 01  C/R: 0 EA: 0
<  TEI: 000        EA: 1
<   M3: 3   P/F: 1 M2: 3 11: 3  [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data





Comments:By: Perry Browning (perryb) 2008-01-30 10:54:35.000-0600

I forgot to mention that a similar report was submitted by collinr on 12-11-04 (ID# 0003021).  Markster's initial response was for collinr to update libpri. Unfortunately, no additional information was provided after Markster's response and the report was closed on 3-1-05. What was the final resolution?

I've been kicking this issue around for about two weeks to insure no stone has been left unturned before seeking further assistance from your group. While I classified thia issue as "minor" (no service affecting condition), it is important that I get an answer as soon as possible since this issue is a major stumbling block toward completing my analysis of the product for potential introduction into the University's network in the near term. (critical users served by DLC).

At this point I am about ready to tear into the code, however I don't want to reinvent the wheel if I don't have to. Any assistance is greatly appreciated.
By: Matthew Fredrickson (mattf) 2008-02-01 15:03:43.000-0600

I am not going to be able to do anything about this do to my lack of GR-303 experience.  You will have to pursue this issue through Digium technical support in order to proceed further.