Addpac ap200d does not understand call answer. Where is the problem?

Question

SIP

There is a task of a forwarding of a telephone line on automatic telephone exchange. There is a piece of iron AddPac AP200D the telephone line is connected to it. The piece of iron is plugged into the "telephone" network by the network port. The PBX is on the same network. All settings on both the PBX and the AP200D are done.
Problem:
When there is an incoming call, the call signaling is normal, but the hook is not recognized.
Incoming
PSTN call -> AP200D -> local network -> PBX -> IP phone
Addition: In September this piece of iron worked even through NAT.

call log

Последовательность: с мобильного позвонил на городской. addpac его перенаправил на внутренний номер 310. на 310 поднимаю трубку, в ней тишина, в мобильном продолжаются гудки. положил трубку на 310 снова пришел звонок. положит трубку мобильного

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.11.07 13:58:05 =~=~=~=~=~=~=~=~=~=~=~=
Welcome to AP200 !
login: root
Password: 
Login incorrect
login: root
Password: 
AP200D  -  Login  : root at tty/1 on Wed Nov  7 13:57:17 2018
GH-FXO# debug voip call
GH-FXO# conf
  Enter configuration commands, one per line. End with CNTL/Z
GH-FXO(config)# debug-p
GH-FXO(config)# debug-port 
GH-FXO(config)# 1<Time0>: SIP_TREGISTER timer timeout. 
2<SIP0>: Adding authentication information
3<SIP35>: Send REGISTER Request 
4<SIP35>: Receive 401 Unauthorized
5<SIP35>: Transaction (35 REGISTER) completed
6<SIP0>: No opaque in authentication 
7<SIP0>: Adding authentication information
8<SIP36>: Send REGISTER Request 
9<SIP36>: Receive 200 OK
10<SIP36>: Transaction (36 REGISTER) completed
11<SIP35>: Set Terminated Success for 35 REGISTER
12<SIP36>: Set Terminated Success for 36 REGISTER
13<CEP000000>: Call Received 
14<CEP000000>: Call Initiated : calledNumber() crv(0) total(0)
15<Call5>: ******************  Call Created status(InitiatedByFXO)  *******************  
16<CEP000000>: Calling number()
17<CEP000000>: Call id(62efe25b-d3e2-17b9-800e-0002a40a33ee) callNum(5)
18<Call5>: MatchAllProcess After Sorted
  <0>  id(1) dest(310) prefer(0) selected(4)
  <1>  id(2) dest(T) prefer(0) selected(0)
19<Call5>: Initiate callee with dial-peer(310) status(CalleeDeterminedAll) id(62efe25b-d3e2-17b9-800e-0002a40a33ee) 
20<NetEP5>: InitiateOutCall: calledNum(310) callingNum() target(sip-server)
21<NetEP5>: DoCall: calledAddr(sip:[email protected]:5060) callingAddr()
22<SIP0>: No authentication information available 
23<SIP5>: Send INVITE Request 
24<SIP5>: Receive 401 Unauthorized
25<SIP5>: Transaction (9 INVITE) completed
26<SIP5>: Send ACK Request 
27<SIP0>: No opaque in authentication 
28<SIP0>: Adding authentication information
29<SIP5>: Send INVITE Request 
30<SIP5>: Receive 100 Trying
31<SIP5>: Transaction (10 INVITE) proceeding 
32<SIP5>: Receive 180 Ringing
33<SIP5>: Transaction (10 INVITE) proceeding 
34<Call5>: Alert from(fffffffe) pseudo(0) inband(0) status(CalleeInitiated)
35<SIP5>: Receive 200 OK
36<SIP5>: Get SIP Audio MediaFormat : 4 
37<SIP5>: SetRemoteSocketInfo : ip(192.168.2.1) port(16082)
38<Call5>: Connected from(fffffffe) 
39<NetEP5>: Call with sip:[email protected] established 
40<SIP5>: Received INVITE OK response 
41<SIP5>: Send ACK Request 
42<SIP5>: Check Event Relation
43<SIP5>: Set Terminated Success for 10 INVITE
44<SIP5>: Receive BYE Request 
45<SIP5>: ReleaseWithNothing 
46<Call5>: Terminated  from(fffffffe) this(Remote:CallClear) before(NULL) forced(0)
47<CEP000000>: DisconnectCall at Busy
48<CEP000000>: StopSignal
49<CEP000000>: Disconnect (0) 
50<NetEP5>: Call TO <sip:[email protected]> terminated reason(Remote:CallClear)
51<CEP000000>: Disconnected(16) at Disconnecting 
52<SIP5>: Set Terminated Success for 9 INVITE
53<Time0>: SIP_TREGISTER timer timeout. 
54<SIP0>: Adding authentication information
55<SIP37>: Send REGISTER Request 
56<SIP37>: Receive 401 Unauthorized
57<SIP37>: Transaction (37 REGISTER) completed
58<SIP0>: No opaque in authentication 
59<SIP0>: Adding authentication information
60<SIP38>: Send REGISTER Request 
61<SIP38>: Receive 200 OK
62<SIP38>: Transaction (38 REGISTER) completed
63<SIP5>: Set Terminated Success for 3 BYE
64<SIP37>: Set Terminated Success for 37 REGISTER
65<SIP38>: Set Terminated Success for 38 REGISTER
exit
GH-FXO# exit

Answer 1

Addpac has been tested on three PBXs. Two of them are ELTEX, one in the office, the second at the provider. And on Asterisk. All have the same problem.
Addpac will return.