[asterisk-users] DAHDI: Inbound BRI call, DDI not presented

[Scott Stingel]

On 6/22/2010 2:03 AM, Tzafrir Cohen wrote:
> On Mon, Jun 21, 2010 at 09:08:02AM -0700, Scott Stingel wrote:
>    
>> Hello-
>>
>> I have a system with one D410P and one B200P (both OpenVox).  All is
>> well with the D410P, inbound and outbound, and I can initiate calls on
>> the B200P  BRI span, but there may be something wrong with my inbound
>> BRI setup:  there is no indication of an inbound call when I dial in to
>> it from the PSTN.
>>
>> When I run "pri intense debug" and make a call to the BRI span, I can
>> see a message containing the DDI that I'm dialing, in this case 336027
>> (BT supplies only the last 6 digits of a delivered number).  See debug
>> output below...
>>      
> Is there anything you see in the dialplan trace itself?
>
> Also, 'intense debug' shows a lot of noise of ISDN layer 2 (Q.921). But
> that is normally not interesting. Do you see anything on a simple 'pri
> debug span 1' (only layer 3 debug)?
>
>    
>> Have I neglected to set up some needed parameter?  This all worked on
>> older boards when using bristuff, but now I want to use dahdi.   My
>> client is in the UK, connected to BT, and I have specified "euroisdn" as
>> the switch type.
>>
>> many thanks
>>
>> ---------------------------------------------------------------------------------------------
>> (snippet during inbound call to "336027")
>>
>> <  Supervisory frame:
>> <  SAPI: 00  C/R: 0 EA: 0
>> <   TEI: 000        EA: 1
>> <  Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
>> <  N(R): 008 P/F: 1
>> <  0 bytes of data
>> -- ACKing all packets from 8 to (but not including) 8
>> -- Stopping T200 timer
>> -- Starting T203 timer
>>      
> Shouldn't an RR be sent back?
>
>    
>> Handling message for SAPI/TEI=0/0
>> TEI: 0 State 7
>> V(S) 8 V(A) 8 V(R) 8
>> K 1, RC 0, l3initiated 0, reject_except 0 ack_pend 0
>> T200 0, N200 3, T203 1
>>
>> <  [ 02 ff 03 08 01 01 05 a1 04 03 80 90 a3 18 01 89 1e 02 84 83 6c 02 21
>> a3 70 07 81 33 33 36 30 32 37 ]
>>
>> <  Unnumbered frame:
>> <  SAPI: 00  C/R: 1 EA: 0
>> <   TEI: 127        EA: 1
>> <    M3: 0   P/F: 0 M2: 0 11: 3  [ UI (unnumbered information) ]
>> <  30 bytes of data
>> Handling message for SAPI/TEI=0/127
>> TEI: 0 State 7
>> V(S) 8 V(A) 8 V(R) 8
>> K 1, RC 0, l3initiated 0, reject_except 0 ack_pend 0
>> T200 0, N200 3, T203 1
>>
>> <  [ 02 ff 03 08 01 01 05 a1 04 03 80 90 a3 18 01 89 1e 02 84 83 6c 02 21
>> a3 70 07 81 33 33 36 30 32 37 ]
>>
>> <  Unnumbered frame:
>> <  SAPI: 00  C/R: 1 EA: 0
>> <   TEI: 127        EA: 1
>> <    M3: 0   P/F: 0 M2: 0 11: 3  [ UI (unnumbered information) ]
>> <  30 bytes of data
>> Handling message for SAPI/TEI=0/127
>> ---------------------------------------------------------------------------------------------
>>      

Thanks, will try the less intense debug.  I thought it was interesting 
however that the incoming DDI was in the message, but not showing up in 
the dialplan trace..
-Scott