ISDN4BSD (HPS version) is going into ports

[Hans Petter Selasky]

On Monday 14 January 2013 16:07:05 Andreas Longwitz wrote:
> For an incoming call I now see correct data in B-channel.
> 
> avm_pci_b_status_read: len=32:
> 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
> avm_pci_b_status_read: len=32:
> 0xf3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3
> ... 12 repeats of last frame ...
> avm_pci_b_status_read: len=18: 0xff03c02101b0000e0506693e5e370304c023
> avm_pci_b_status_read: len=18: 0xff03c02101b1000e0506693e5e370304c023
> avm_pci_b_status_read: len=18: 0xff03c02101b2000e0506693e5e370304c023
> avm_pci_b_status_read: len=18: 0xff03c02101b3000e0506693e5e370304c023
> ...
> 
> The frames of length 18 are exactly the frames I see on the remote side
> by isdndecode. But my local isdndecode does not see these B-channel
> messages, I don't know why.

Hi,

Do you know what mode the chip is running in for the B-channels?

HDLC or so-called transparent mode (no bit-destuffing). By default the AVM PCI 
driver is setup to use HDLC emulation, and expects that the chip is configured 
for transparent mode. Valid HDLC flags start like 0x7E, and that is what I 
would expect. Else something is wrong somewhere. 

[Incoming data] -> [HDLC table decoder] -> [isdndecode]

No data in isdndecode means that the HDLC table decoder is not getting what it 
expects.

--HPS