Re: "MPH_DEACTIVATE_IND" message.... (now with single port HFC board)

Am 26.03.2014 07:03, schrieb fabio antonini:
> Hi Karsten
> thanks a lot for the help
> At the moment I have no info about the P2P or P2MP configuration of the
> line. Anyway the remote equipment (A custom board running hisax driver
> on XHFC_1SU configured as NT) has been succesfully used to establish a
> PPP connection with my Cologne XHFC_4SU evaluation board using an old
> Hisax driver for xhfc_su. Anyway I will try to get this info about
> P2P/P2MP as soon as possible.
> 
> Anyway I have tried to run misdntestlayer3 as you suggested.
> Here below the command issued and the output messages
> 
> ~ # misdntestlayer3 -P -c0 -n111111 -v5   
> mISDN Test L3 2.0
> 01.01.1970 11:57:19.926843  mISDN kernel version 1.01.29 (git.misdn.eu)
> found
> 01.01.1970 11:57:19.927090  mISDN user   version 1.01.31 found
> 01.01.1970 11:57:19.927207  mISDN library interface version 2 release 5
> 01.01.1970 11:57:20.235104  open card 0 with 2 channels options(50003)
> 01.01.1970 11:57:27.357470  from L3 cmd MPH_DEACTIVATE_IND (602) pid(10000)
> 01.01.1970 11:57:27.357734  got message (602) with pid(10000) but not
> ff008001
> 01.01.1970 11:57:27.358354  from L3 cmd FREE_PID (11001) pid(ff008001)
> 01.01.1970 11:57:27.358917  from L3 cmd L2IDLE (12002) pid(0)
> 01.01.1970 11:57:27.359067  got message (12002) with pid(0) but not ffffffff
> 01.01.1970 11:57:27.359179  from L3 cmd L2RELEASE (12001) pid(0)
> 01.01.1970 11:57:27.359287  got message (12001) with pid(0) but not ffffffff
> 01.01.1970 11:57:27.359500  control pipe unhandeld cmd 11001 - FREE_PID
> 01.01.1970 11:57:27.359636  Worker terminated with 0
> 
For some reason the L1 never goes active. Can you please try a incomming
call, so the other side does the activation ?


> Messages from kernel at the same time:
> 
> base_sock_release(8ede4340) sk=8c370200
> base_sock_release(8ede4340) sk=8c370200
> XHFC.1: xhfc_dctrl: cmd:100 8f5dde20
> XHFC.1: open_dchannel: dev(0) open from c020f130 mode 1
> create_l2entity: ret 1 0
> XHFC.1: xhfc_dctrl: cmd:100 8f5ddd78
> XHFC.1: open_dchannel: dev(0) open from c0212fa4 mode 1
> XHFC.1: xhfc_dctrl: cmd:100 8f5dddc8
> XHFC.1: open_dchannel: dev(0) open from c02198d0 mode 1
> create_l2entity: ret 2 0
> XHFC.1: xhfc_l2l1D: PH_ACTIVATE_REQ TE
> xhfc_ph_command XHFC.1: L1_ACTIVATE_TE (0)
> XHFC.1: xhfc_l1callback cmd 0x8a02
> HW_RESET_REQ XHFC.1: xhfc_l1callback cmd *0x8a02*
> XHFC.1: xhfc_l1callback cmd 0x202
> XHFC.1: xhfc_dctrl: cmd:200 00000000
> XHFC.1: xhfc_dctrl: dev(0) close from c02131c0
> XHFC.1: xhfc_dctrl: cmd:200 00000000
> XHFC.1: xhfc_dctrl: dev(0) close from c02132bc
> XHFC.1: xhfc_dctrl: cmd:200 00000000
> XHFC.1: xhfc_dctrl: dev(0) close from c02194b8
> 
> Thanks a lot for your time
> best regards
> 
> fabio
> On 03/25/2014 10:05 PM, Karsten Keil wrote:
>> Am 25.03.2014 10:07, schrieb fabio antonini:
>>> Hi Doug
>>> I have a scenario not far from yours and I'm facing the same problem.
>>> I have a 4 channels cologne evalboard based on XHFC_4SU
>>>
>>> ~ # misdn_info
>>>
>>> Found 4 ports
>>>   Port  0 'XHFC.1':          TE/NT-mode BRI S/T (for phone lines & phones)
>>>                               2 B-channels: 1-2
>>>                                 B-protocols: RAW HDLC X75slp L2:DSP
>>> L2:DSPHDLC
>>>   --------
>>>   Port  1 'XHFC.2':          TE/NT-mode BRI S/T (for phone lines & phones)
>>>                               2 B-channels: 1-2
>>>                                 B-protocols: RAW HDLC X75slp L2:DSP
>>> L2:DSPHDLC
>>>   --------
>>>   Port  2 'XHFC.3':          TE/NT-mode BRI S/T (for phone lines & phones)
>>>                               2 B-channels: 1-2
>>>                                 B-protocols: RAW HDLC X75slp L2:DSP
>>> L2:DSPHDLC
>>>   --------
>>>   Port  3 'XHFC.4':          TE/NT-mode BRI S/T (for phone lines & phones)
>>>                               2 B-channels: 1-2
>>>                                 B-protocols: RAW HDLC X75slp L2:DSP
>>> L2:DSPHDLC
>>>
>>> I have connected the first channel (TE mode) to an external equipment
>>> (working fine for sure) configured as NT.
>>>
>> Does this be a P2P or P2MP type of line ? misdntestcon only works for
>> P2MP lines.
>> You should try misdntestlayer3 -P for P2P lines.
>>
>> Karsten
>>
>> _______________________________________________
>> isdn4linux mailing list
>> [email protected]
>> https://www.isdn4linux.de/mailman/listinfo/isdn4linux
>>
>> .
>>
>