SOLVED Clearly Anywhere for Incredible PBX 2020 PUBLIC

[Tonyclewis]

Here is a great video from CrossTalk on Clearly Anywhere.

 

[phinphan]

EDIT - just got it working. Had to change some names and passwords in user management but it works now as far as connecting and calling, no inbound to it yet but I'm working on it.

Thanks Ward, i keep getting screwed up in the User Management section but I will give it another try later. I have a hard time wrapping myself around a user as opposed to an extension and how to make it work.

Ward, outbound is working great. Cant get inbound to the android working. What number do I call for it? I thought I had it registered as an extension but that does not seem to work.

 

[Tonyclewis]

You would call the extension number that the user is linked to in user manager. In user manager under a user it has a linked extension. That is the extension you call.

 

[phinphan]

Thanks to all got it working. inbound is a little flaky so far and for my install, I have to run portknocker every time the IP changes on my phone. That is the best feature of the 3cx client, no worries about ip addresses. Now if I could just get an android app that will automatically update my ip address.

 

[fredzimm]

Ward, outbound is working great. Cant get inbound to the android working. What number do I call for it? I thought I had it registered as an extension but that does not seem to work.

I'm seeing a similar issue, I think it has to do with how Android manages background apps. I've reached out to tech support on this. If you're completing calls you're registered.

 

[phinphan]

You would call the extension number that the user is linked to in user manager. In user manager under a user it has a linked extension. That is the extension you call.

Thanks Tony. I could not get an inbound call unless I first made a call with the app to the office. Then inbound works fine.

 

[Tonyclewis]

For inbound to work you need to have your sip ports opened. I know ward I’m had a public version of incredible that opens the sip ports. I will let ward reply on this.

 

[fredzimm]

For inbound to work you need to have your sip ports opened. I know ward I’m had a public version of incredible that opens the sip ports. I will let ward reply on this.

Looks like that's my issue as well. I'll watch for Ward's guide before taking a wrench to the firewall.

 

[wardmundy]

Just follow the Incredible PBX 2020 PUBLIC tutorial to convert your Incredible PBX 2020 server into a PUBLIC-facing server. Don't use the standard Incredible PBX 2020 platform because SIP access is blocked unless the user's IP address is on the firewall whitelist, and you want to keep it that way unless you don't mind a huge phone bill.

YOU DO NOT WANT TO OPEN SIP ACCESS ON THE STANDARD INCREDIBLE PBX SERVER. THAT'S WHAT THE PUBLIC RELEASE IS FOR!!

 

[wardmundy]

Tutorial coming Monday to Nerd Vittles.

 

[ostridge]

Ward, outb

Its easy to insert a link to a particular member: just type the at symbol and 1st few characters of the member name, click the pop-up and you are done. E.g. '@phi' @phinphan

 

[wardmundy]

Clearly Anywhere: The Ultimate Mobile User VoIP Companion – Nerd Vittles

nerdvittles.com

 

[phinphan]

@wardmundy can I convert my existing non-Public 2020 to PUBLIC and keep my existing connections? In other words, can I access a public 2020 server the same way I always do with ./add-ip or ./add-fqdn? I do not want to have to redo all the existing connections which work from static ip connections.

 

[macarte]

How would that work on the Raspberry Pi 4 - 2020 installs? The port knocker doesn't seem like the ideal solution and having an OpenVPN connection permanently established might come in the way of other business activities...

Any suggestions?

 

[tbrummell]

Hard for them to make a sale when you can't get past the Shipping method in the Cart.

 

[wardmundy]

@tbrummell: Thanks. Will pass it along to @Tonyclewis. Inauguration Day is always full of surprises.

UPDATE: Should be fixed now.

 

[wardmundy]

@wardmundy can I convert my existing non-Public 2020 to PUBLIC and keep my existing connections? In other words, can I access a public 2020 server the same way I always do with ./add-ip or ./add-fqdn? I do not want to have to redo all the existing connections which work from static ip connections.

You'd need to back out your add-ip and add-fqdn entries and then reenter them after the migration. Registrations must be by FQDN ONLY after migration. Very different design.

 

[billsimon]

I thought this was supposed to be a fairly automatic install thanks to the FreePBX module. Under what circumstances would that be expected? Need for a multi-step tutorial is disappointing.

 

[phinphan]

You'd need to back out your add-ip and add-fqdn entries and then reenter them after the migration. Registrations must be by FQDN ONLY after migration. Very different design.

Thanks. An after hours project then!

 

[dhoppy]

The public version of IPBX 2020 doesn't allow for easy access to the UCP for users. Is there a way for an ADMIN to get the QR codes for auto-provisioning and email it out?