[asterisk-bugs] [Asterisk 0011870]: Problem connecting Asterisk to UMC-1000 using GR-303

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11870 
====================================================================== 
Reported By:                PerryB
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11870
Category:                   Core/Channels
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-29-2008 14:06 CST
Last Modified:              01-30-2008 10:54 CST
====================================================================== 
Summary:                    Problem connecting Asterisk to UMC-1000 using GR-303
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?
====================================================================== 

---------------------------------------------------------------------- 
 PerryB - 01-30-08 10:54  
---------------------------------------------------------------------- 
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. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-30-08 10:54  PerryB         Note Added: 0081442                          
======================================================================