send Telegram -> RC work, RC-> Telegram no. And a few more questions

Description:

Steps to reproduce:

1. bash -c "$(curl https://install.rocket.chat)" //no proxy and url RC https://testrc.domen.com/
2. install nginx + lets
3. Go site, auto redirect create user, create. create info org, create info server (type private, fa2 disable), Register for access: YES. I agree to the Terms & Privacy Policy - YES. Your workspace is ready to go 🎉 Good)
4. Next admin panel /admin/info -> /admin/marketplace -> telegram -> install -> Marketplace login required -> Authorization -> /admin/cloud -> https://cloud.rocket.chat/ create user, verif email, click plus and Register self-managed -> internet access -> copy key -> paste /admin/cloud and click Connection -> good -> click Login to Rocket.Chat Cloud -> authorization -> good
5. Next setting /omnichannel/current -> omnichannel/managers manager add me -> /omnichannel/agents agent add me -> /omnichannel/departments create name = "ALL" click enable, insert email, click save
6. Next admin panel /admin/info -> /admin/marketplace -> telegram -> install -> I agree with the Terms & Privacy Policy yes ->
   go tg @BotFather, create bot, copy key -> paste /admin/marketplace/details/fc96e832-5472-49e4-aace-1521a7ebeaa6/1.0.2 -> Default Department Id or Name = ALL -> Service Unavailable Message = "Failed or if no agents are online" -> Welcome Message = "Kyky" -> Conversation Finished Message = "Finish" -> click save
7. Settings /admin/Omnichannel
   
8. Go home site.
9. screen
10. I sent from tg, and I don't see where the messages or the queue are
11. Go /omnichannel/current and lo and behold it is here, but the question is why not on the main, click
12. click
13. 

Expected behavior:

1. At least two-way communication)))
2. Instant display in the chat list (queue), because it's stupid to go into the settings every time.
3. Or auto-acceptance by the first free operator.

Actual behavior:

Paragraph(Steps to reproduce) 10 and 13 above

Server Setup Information:

• Version of Rocket.Chat Server: 3.17.1, app 1.27.1
• Operating System: OS Ubuntu 20.04 (I also tried on Debian 9, Centos 8)
• Deployment Method: bash -c "$(curl https://install.rocket.chat)" or https://docs.rocket.chat/installing-and-updating/manual-installation/ubuntu (manual)
• Number of Running Instances: 1
• DB Replicaset Oplog: yes
• NodeJS Version: in Panel v12.22.5, cmd node -v (12.14.0), cmd nodejs -v ('nodejs' not found, but can be installed with: apt install nodejs)
• MongoDB Version: in panel 4.0.26

Client Setup Information

• Desktop App or Browser Version: chrome
• Operating System: win10

Additional context

Relevant logs:

/admin/view-logs clear

Perhaps this screenshot will help you

Help me, from me for coffee))

tried to install this version, it also did not help
https://github.com/RocketChat/Rocket.Chat/issues/20241#issuecomment-851264388

Reproduce the Telegram omnichannel setup using the listed Rocket.Chat version, then compare messages shown in /omnichannel/current with the main chat list and the screenshots. Confirm the expected two-way communication, queue visibility, and agent assignment behavior before identifying the affected subsystem.