Dahdi does not process caller id from Rostelecom, what am I doing wrong?

Question

linux

Hello!
Connection diagram:
Rostelecom noodles on a patch panel -> asteroid 30fxo in broadcast -> hp procurve 1910 vlan 29 -> heartbeat cluster asterisk 11 -> Yealink t21.
They call via vulture, only incoming from Rostelecom.
chan_dahdi.conf (currently, constantly correcting something in search of a solution)

[channels]
;
relaxdtmf=yes   ;necessary on bad lines only...
rxflash=850     ;flash is an ONHOOK < rxflash
rxwink=300
useincomingcalleridondahditransfer=yes
language = ru
busydetect = yes
busycount=3
pulsedial = no
pulse = yes
cancallforward = yes
usecallerid = yes
callerid = asreceived
hidecallerid = no
sendcalleridafter = 3
immediate=no
callwaitingcallerid = yes
cidsignalling = v23
cidstart = ring
callreturn = yes
echocancel = yes
echotraining = no
echocancelwhenbridged = yes
rxgain = 0.0
txgain = 0.0
callprogress=yes

context=incoming_03
signalling=fxs_ls
channel= 7-30


context=incoming_03
cidsignalling = bell
cidstart = ring
signalling=fxs_ls
channel= 2-6

context=st_vr_k
signalling=fxs_ls
channel = 1

system.conf

#Parabel Asteroid
dynamic=eth,eth1/00:55:55:55:55:00,30,1
alaw=1-30
fxsls=1-7
fxsls=8-15
fxsls=16-22
fxsls=23-30
echocanceller=oslec,1-30
loadzone=ru
defaultzone=ru

Now about the interesting. 2 groups of incoming lines come from different city telephone exchanges - 260XXXX and 264XXXX. When you call 260 - the number is determined. When calling to 264, it is not detected (denoted as (260+ 264-)). I call the chief engineer in RT, he says our equipment is crooked. If you connect some Panasonic with a display there, it is determined. I rested, I say - check for yourself, I can’t give birth to this caller id if I didn’t see it on my equipment, but within the same board it works on neighboring ports with the same settings. I started looking, they say they have fsk on both Euroaons, but it’s a little different, but it doesn’t know how to change the settings of the piece of iron on the PBX, on the other hand it won’t work either, contact the vendor, why our native Russian equipment does not want Caller ID certified in Russia.
Initially set cidsignalling = bell (260+ 264-). Installed cidsignalling = v23 became 260- 264+. I went to smoke for joy, I came - it became 260-264-. Returned back to bell - 260+ 264-. Dahdi, Aster and a piece of iron rebooted. I have never seen such a miracle.
Debug didn't show anything either. Here is an example (on one it was determined, on the other not)

[Dec 13 15:23:06] DEBUG[16753] chan_dahdi.c: Monitor doohicky got event Ring Begin on channel 7
[Dec 13 15:23:06] DEBUG[16753] chan_dahdi.c: Monitor doohicky got event Ring/Answered on channel 7
[Dec 13 15:23:08] DEBUG[16777][C-0000003c] chan_dahdi.c: CallerID number: 84732342773, name: (null), flags=4
[Dec 13 15:23:08] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 3 on channel DAHDI/7-1
[Dec 13 15:23:08] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 22 on channel DAHDI/7-1
[Dec 13 15:23:08] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 33 on channel DAHDI/7-1
[Dec 13 15:23:08] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 33 on channel DAHDI/7-1
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 33 on channel DAHDI/7-1
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 22 on channel DAHDI/7-1
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Set option TONE VERIFY, mode: MUTECONF(1) on DAHDI/7-1
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication -1 on channel DAHDI/7-1
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Enabled echo cancellation on channel 7
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: No echo training requested
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication -1 on channel DAHDI/7-1
[Dec 13 15:23:14] DEBUG[16777][C-0000003c] chan_dahdi.c: Requested indication 20 on channel DAHDI/7-1
[Dec 13 15:23:19] DEBUG[16753] chan_dahdi.c: Monitor doohicky got event Ring Begin on channel 5
[Dec 13 15:23:20] DEBUG[16753] chan_dahdi.c: Monitor doohicky got event Ring/Answered on channel 5
[Dec 13 15:23:24] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 3 on channel DAHDI/5-1
[Dec 13 15:23:24] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 22 on channel DAHDI/5-1
[Dec 13 15:23:24] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 33 on channel DAHDI/5-1
[Dec 13 15:23:24] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 33 on channel DAHDI/5-1
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 33 on channel DAHDI/5-1
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 22 on channel DAHDI/5-1
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Set option TONE VERIFY, mode: MUTECONF(1) on DAHDI/5-1
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication -1 on channel DAHDI/5-1
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Enabled echo cancellation on channel 5
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: No echo training requested
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication -1 on channel DAHDI/5-1
[Dec 13 15:23:27] DEBUG[16779][C-0000003d] chan_dahdi.c: Requested indication 20 on channel DAHDI/5-1

Share your experience in setting up the Rostelecom Caller id, I've been trying to set it up in different ways for 2 days now. I need advice from more experienced people.
Thanks in advance.
OBN: The question is removed, just sorted it out.

context=incoming_03
signalling=fxs_ls
cidsignalling = v23
cidstart = ring
channel= 7-30


context=incoming_03
cidsignalling = dtmf
cidstart = dtmf
signalling=fxs_ls
channel= 2-6

context=st_vr_k
signalling=fxs_ls
channel = 1

I did not expect this from Rostelecom)

Answer 1

OBN: The question is removed, just sorted it out.