[Home]

Summary:ASTERISK-02966: GR-303 Compatibility issues with AFC AccessMAX / UMC1000
Reporter:collinr (collinr)Labels:
Date Opened:2004-12-11 12:32:50.000-0600Date Closed:2011-06-07 14:10:43
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) ast-configs.txt
( 1) umc1000.txt
( 2) umc-asterisk-debug-2004-12-13.txt
Description:When attempting to use GR-303 between Asterisk and the UMC1000 I am having difficulty. Occasionally the TMC channel (24) will come up on both the asterisk side and the UMC side.  The EOC channel (12) never comes up on the UMC side.  Asterisk does not seem to have any references  to the EOC (other than in libpri).

The asterisk box under pri intense debug will continuously display the following message:

> Unnumbered frame:
> SAPI: 01  C/R: 1 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
Sending Set Asynchronous Balanced Mode Extended    

I also get the debug message below occasionally:

 == Primary D-Channel on span 2 down
Dec 11 13:27:24 WARNING[13477]: chan_zap.c:1941 pri_find_dchan: No D-channels available!  Using Primary on channel anyway 48!



Asterisk configuration file snippets and umc1000 configs attached.

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

http://www.afc.com/solutions/application.asp?application=2&solution=6&subapplication=118#Learn%20More

http://www.afc.com/documents/literature_library/GR303AppsNote_ADV.pdf
Comments:By: Mark Spencer (markster) 2004-12-12 18:42:48.000-0600

Update your libpri and try again.
By: collinr (collinr) 2004-12-13 07:58:53.000-0600

The TMC channel seems to come up now.  The EOC Channel still doesn't come up.

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

LET GR303 Group 1


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

EOCA        LET-1-3-12  Down           EOCB        LET-1-4-12  Down
TMCA        LET-1-3-24  Active         TMCB        LET-1-4-24  Standby

DS1 1   Pri LET-1-3     In-Service     DS1 15      None
DS1 2   Sec LET-1-4     In-Service     DS1 16      None



dyr-ast1*CLI> pri show span 2
Primary D-channel: 48
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
T313 Timer: 4000
N200 Counter: 3
By: collinr (collinr) 2004-12-13 09:40:16.000-0600

When I make an inbound call about 50% of the time I get a disconnect and the other 50% of the time I get ringing from the calling device.  The gr303 end point does not ring however (though I can pick the phone up and answer it).

when trying to dialout from the gr303 endpoint I seem to be getting this error quite a bit:

Dec 13 10:30:56 WARNING[26693]: chan_zap.c:5780 handle_init_event: Don't know how to handle ring/answer with signalling GR-303 Signalling with FXOKS on channel 46

Dec 13 10:38:04 WARNING[26957]: chan_zap.c:5780 handle_init_event: Don't know how to handle ring/answer with signalling GR-303 Signalling with FXOKS on channel 47
By: collinr (collinr) 2004-12-13 15:41:19.000-0600

I resolved the issue with an audible ringing tone.  Now we are just dealing with the fact that inbound calls to the gr303 group from asterisk to the umc only complete some of the time and usually end like this:

-- Executing Dial("Zap/23-1", "Zap/1:7") in new stack
   -- Called 1:7
   -- Accepting call from '9897206000' to '9897201122' on channel 0/23, span 1
   -- Zap/1:7-1 is ringing
   -- Zap/1:7-1 answered Zap/23-1
   -- Attempting native bridge of Zap/23-1 and Zap/1:7-1
   -- Hungup 'Zap/1:7-1'
 == Spawn extension (inbound, 9897201122, 1) exited non-zero on 'Zap/23-1'
   -- Hungup 'Zap/23-1'


So it appears that the call is answered, though I am not actually answering it.
Debug log attached.
By: Mark Spencer (markster) 2004-12-14 15:00:06.000-0600

It would appear from your debug that your switch is placing "answered" signalling on the line.
By: collinr (collinr) 2004-12-14 15:41:23.000-0600

I am reading this "answer" as being some sort of signalling anomaly in the signalling between the UMC and Asterisk.  I do have 4 options for switch type on my GR-303: 5ESS, DMS, EWSD, and GTD5.  I have tried all of them with similar results.
By: nick (nick) 2004-12-31 12:45:39.000-0600

Does this bug persistent with latest CVS?
By: twisted (twisted) 2005-01-09 22:35:02.000-0600

collinr: your response is reqested - is this still an issue?
By: collinr (collinr) 2005-01-10 08:30:53.000-0600

This is still an issue.  I believe Mark was going to work on it after his return from his holiday vacation.
By: Olle Johansson (oej) 2005-02-13 13:02:51.000-0600

This bug has been sleeping for a month... Anyone else than Mark that can fix this, we can't place everything on his shoulders? Creslin?
By: Mark Spencer (markster) 2005-02-28 00:33:36.000-0600

This should go ahead and get moved to digium tech support whenever you're ready to try again.