Summary:	ASTERISK-02904: E1 PRI won't bring b-channels up
Reporter:	nirsim (nirsim)	Labels:
Date Opened:	2004-11-30 08:16:32.000-0600	Date Closed:	2011-06-07 14:10:10
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) pri_debug_from_Asterisk.txt ( 1) pri_debug_from_Carrier
Description:	Ok, i'm not entirely sure if this is the correct place to put this, but as I've been combating this issue for a month now, I believe it may constitue a bug/tweak in Asterisk. I'll describe the situation: I've got a box connected to 3 E1 circuits. 2 Circuits are working fine and dandy, no problems. The third connected circuit shows the D-channel as up, however, no b-channels will come up. I've been at this problem with the carrier for a month now, and we all come empty handed. Now, in order to validate that everything from point-of-origin to point of presentation works fine, we've connected a cisco PSTN gateway to the line, and it came up, we managed to make calls, no problem. At that point, I thought to myself - "well, maybe the port is faulty, or the cabling", so, I've replaced everything. Even the TE410P card was replaced by a new one, and yet, the problem persists. Now, I've ran a 'pri intense debug' on the circuit, and I noticed the following messages on the console, while the line tries to come up: > [ 00 01 00 00 08 02 00 00 46 18 03 a9 83 8b 79 01 80 ] > Informational frame: > SAPI: 00  C/R: 0 EA: 0 >  TEI: 000        EA: 1 > N(S): 000   0: 0 > N(R): 000   P: 0 > 13 bytes of data -- Restarting T203 counter Stopping T_203 timer Starting T_200 timer > Protocol Discriminator: Q.931 (8)  len=13 > Call Ref: len= 2 (reference 0/0x0) (Originator) > Message type: RESTART (70) > [18 03 a9 83 8b] > Channel ID (len= 5) [ Ext: 1  IntID: Implicit, PRI Spare: 0, Exclusive Dchan: 0 >                        ChanSel: Reserved >                       Ext: 1  Coding: 0   Number Specified   Channel Type: 3 >                       Ext: 1  Channel: 11 ] > [79 01 80] > Restart Indentifier (len= 3) [ Ext: 1  Spare: 0  Resetting Indicated Channel (0) ] < [ 00 01 01 02 ] < Supervisory frame: < SAPI: 00  C/R: 0 EA: 0 <  TEI: 000        EA: 1 < Zero: 0     S: 0 01: 1  [ RR (receive ready) ] < N(R): 001 P/F: 0 < 0 bytes of data -- ACKing all packets from 0 to (but not including) 1 -- ACKing packet 0, new txqueue is -1 (-1 means empty) -- Since there was nothing left, stopping T200 counter -- Nothing left, starting T203 counter -- Restarting T203 counter Now, I'm not an ISDN nor a switch expert, but it simply looked a little funky to me. I'm again not sure if this is a bug, or a configuration issue, or maybe just a simple tweak that needs to be done, but I'm at a loss here. Attached are 2 debugs, one from the Asterisk 'pri intense debug span 2' command, and one from the point of origin switch. On the second debug, 4B stands for the Asterisk box and 4A inidicates the point of origin switch.
Comments:	By: Mark Spencer (markster) 2004-11-30 09:08:49.000-0600 This is a technical support question, not a software bug, please go through Digium technical support (support@digium.com).