Block remote tunnel is ON and could not be disabled

Andrea Cataldo

Silver Partner
Advanced Certified
Joined
Mar 21, 2023
Messages
6
Reaction score
1
I have an installation updated from v18 where a user has the block remote tunnel enabled. After the migration to v20 the user is "promoted" to use the App on his mobile App but with the new version I can't find anymore the checkbox to deflag

SIP request (REGISTER) from 127.0.0.1 was rejected. Reason: Block remote tunnel is ON.

Other users that was enabled with v18 doesn't has had any issue after the upgrade to v20 and newly created user can connect via mobile App and use it without any problem

Is possible to re-enable the tunnel connection for an extension previously blocked without delete and recreate the extension?
 
Hello, isn't it there what you are searching? in users options/options
1748683830383.png
 
  • Like
Reactions: Evolute IT
Thanks for the reply. That option is for remote extension connected without tunnel. Nothing change on the extesion (and in the log too) with this check box enablead or disabled.

I've tried this solution hoping that it will be change the beaviour for tunnel connection too,but nothing change
 
Hi,

Remote tunnel connections are enabled always - check if the user app needs to be reprovisioned via QR and/or if there IP ended up in the blacklist for some reason.

Best,
K.
 
Thanks,

same things that I know about v20. This installation is an upgrade from v18 (and v16 and earlier) where the feauture was clearly present. Same mobile phone, same IP, different extension (one newly created and the one with the tunnel connection explicit disabled in v18) the first works without any problem and second not.
 
A quick solution might be to delete and recreate the problem extension. Take a backup first of course in case you need to roll back this change.
 
  • Like
Reactions: AWS2P
A quick solution might be to delete and recreate the problem extension. Take a backup first of course in case you need to roll back this change.
Yes, this is the first solution that I've found... The problem is that deleting the extension will lose some information and it will be desirable to mantain it
 
A thought, if this is a flag that remained from V18, if you take a backup now perhaps it will be visible in it, and you can change its value and restore. This is simply a thought.
 
It seems that with Update 5 the problem is solved.

I've made a comparison between previous backup anche U5 backup and for the extension the XML property BLOCKREMOTETUNNEL is disappeared
 
  • Like
Reactions: K_SAK

Latest Posts

Members Online Now

Forum statistics

Threads
111,844
Messages
589,330
Members
164,680
Latest member
JV J