3CX App not working v20

[iridium79]

Hi, I have added a new user in the system, provisioning works fine on the app. User cannot make outgoing calls. In the Activity logs it says: Block Remote Tunnel is ON. I do not see an option to disable or enable that feature in the user. Please help... Did it get moved somewhere else?

Thank you

 

[Alphabetic]

Whats under "Options > Options" in the ext?

 

[iridium79]

Block remote non-tunnel connections is checked.

 

[Vali_3CX]

@iridium79
Yes, turn it OFF (uncheck it) our apps requires tunnel for SIP calls.

 

[iridium79]

@iridium79
Yes, turn it OFF (uncheck it) our apps requires tunnel for SIP calls.

I unchecked it same result

 

[Vali_3CX]

Has the Firewall Checker passed the tunnel test? Is port 5090 open? From a command line you can try a telnet to your pbx on port 5090.

 

[iridium79]

I have other 3cx apps on phones and those work properly, its all the new ones i created that do not work.. All of the other extensions also have the Block remote non-tunnel extensions checked, and they work. yes port 5090 is open.

 

[mgroom]

Hi, I have added a new user in the system, provisioning works fine on the app. User cannot make outgoing calls. In the Activity logs it says: Block Remote Tunnel is ON. I do not see an option to disable or enable that feature in the user. Please help... Did it get moved somewhere else?

Thank you

Can the user dial internal extensions from the app? Does the app show that the profile is active and ready? Can the user receive calls?

 

[iridium79]

Can the user dial internal extensions from the app? Does the app show that the profile is active and ready? Can the user receive calls?

That's the weird part it says "Ready for Calls". and when they try to call internal extension or an outgoing call - fast busy and then for a split second says invalid credentials and goes back to "Ready for Calls". Also the user cannot receive calls.

 

[mgroom]

That's the weird part it says "Ready for Calls". and when they try to call internal extension or an outgoing call - fast busy and then for a split second says invalid credentials and goes back to "Ready for Calls". Also the user cannot receive calls.

Based on this weird behavior and the fact that this is in on-premise i am assuming that something on the internal dns record is messed up. Has the user disabled wifi on the phone and then tried.

 

[iridium79]

Based on this weird behavior and the fact that this is in on-premise i am assuming that something on the internal dns record is messed up. Has the user disabled wifi on the phone and then tried.

We have tried both on wifi and off. Its only new users... existing users work perfectly fine. I am going to try with v18 and see if that changes anything.

 

[mgroom]

We have tried both on wifi and off. Its only new users... existing users work perfectly fine. I am going to try with v18 and see if that changes anything.

Are you on RC3. I am with my test system and just created a new user and everything default on the user and it connected right up and was able to make calls.

 

[iridium79]

Could it be something got corrupted on the upgrade from v18 to v20? This is the version im on: Version 20.0 Update 0 (Build 1620 Beta)

 

[mgroom]

Possibly but you’re using the beta I would recommend upgrading all the way to release candidate three and see if that fixes the issue

 

[mgroom]

Just quickly looking at mine. I’m only on version 20 16 09 beta which is release candidate three not sure what 1620 is.

 

[iridium79]

Just quickly looking at mine. I’m only on version 20 16 09 beta which is release candidate three not sure what 1620 is.

I think thats RC4 system updated today.

 

[mgroom]

I think thats RC4 system updated today.

I see. I did not realize that another release candidate was out already.

 

[AndreasPo_3CX]

Hi @iridium79

Is this a new extension or an extension that was already on the system since V18 and was now assigned to a new person?