SOLVED Clearly Anywhere for Incredible PBX 2020 PUBLIC

[jerrm]

I did some more Android Groundwire testing, and it turns out it is does sporadically pick up the outbound CNAM info. It is more likely to pick up the info of the remote end if the dialed number actually rings (I often test with a fax number).

When the in-call display and history never reflect the name, the call ending popup seems to always (in my limited testing) say "Call with 'Proper Name Info' Ended".

My guess is the Acrobit SIP stack underneath is processing the info, but the display/history code doesn't expect the name to change as late in the flow as the Outbound-CNAM module processes.

It's been a while since I tested Groundwire, but it didn't do this well last time I tested.

I also loaded up Android Clearly Anywhere and it behaves similarly, and seems slightly more likely to pick up the name, although it is still far from 100%.

Apple testing this week, with luck it will do better.

 

[jerrm]

Also - for anyone that cares, the Clearly Anywhere module loads and works fine under a Debian 10/PHP 7.3 environment.

 

[tbrummell]

Clearly Anywhere and Groundwire (and Sangoma Connect) use the Acrobits softphone SDK thus the similarities.

Also explains why the UI's are so similar. I figured they were both using a Google SDK, guess not.

 

[tbrummell]

Try using our public.conf Web Access template on your PUBLIC server. Haven't seen a problem with the revised code.

This is what I followed. Once complete the results were as follows:
FQDN via VPN link: FreePBX UI
FQDN via Internet: no response from server
Server IP via Internet: Forbidden page (as expected)

Lack of response was also confirmed by tailing httpd logs, and seeing nothing except when the server IP was used...

80 and 8080 were both listening as confirmed with netstat -an. iptables was open as confirmed with iptables -vnL

I'll try again today since it's a holiday here, Happy Thanksgiving to my .ca friends!

 

[tbrummell]

I'll try again today since it's a holiday here

Well, I don't know what I did wrong yesterday, but today I appear to have gotten the expected result...
FQDN via VPN link: FreePBX UI
FQDN via Internet: FreePBX UI (is this expected, I suspect yes...)
FQDN:8080 via Internet: UCP
Server IP via Internet: Forbidden page (as expected)
Server IP:8080 via Internet: UCP (this is probably not expected, and not good if you're trying to hide the UCP from general use.)

And after all of that, the CA still has the same error.

 

[tbrummell]

Server IP:8080 via Internet: UCP (this is probably not expected, and not good if you're trying to hide the UCP from general use.)

Fixed it by adding this to public.conf, right after the first :80 block of code.

<virtualhost *:8080>
ServerAdmin [email protected]
ServerName 111.112.113.114
Redirect 403 /
UseCanonicalName Off
UserDir disabled
</virtualhost>

 

[wardmundy]

Fixed it by adding this to public.conf, right after the first :80 block of code.

<virtualhost *:8080>
ServerAdmin [email protected]
ServerName 111.112.113.114
Redirect 403 /
UseCanonicalName Off
UserDir disabled
</virtualhost>

Updated tutorial. Thanks.

 

[jerrm]

Groundwire & Clearly Anywhere Android seem nearly 100% OK for outbound cnam on FreePBX 15. I say "nearly" because I had some issues yesterday that I can't recreate today. What was sporadic seems solid today. Yesterday was with the TV going and other distractions, I wonder if I got confused about which app and account I was using.

Groundwire does have an issue updating the display if the call isn't answered. CA seems OK in that regard.

The prior Groundwire issues appear to be from an older FPBXv13 test box I was using for testing phones. That box was actually using outbound predial hook dialplan for cnam and not the module. Multiple brand desk phones, GS Wave and Bria all work fine with that server but not Groundwire. So the Acrobits stack appears to be a little finicky, but will work with the current release of FreePBX with the outcnam module.

CA for Apple also works fine with FreePBX 15 and the outcnam module.

I'll test CA as my daily driver for a week or two and it's likely to become my deployed preference, but unless it's updated to support multiple accounts GS Wave will continue to be my personal softphone.

 

[jerrm]

One day in and my biggest complaint - Clearly Anywhere needs a DARK MODE!!!!!

 

[wardmundy]

@jerrm @tbrummell @jbcameraguy @Hometech With special thanks to the Clearly Anywhere folks (Tony and Brian) for solving this, we now have PUBLIC server access working as intended.

By default, PUBLIC server web access to all apps including FreePBX, UCP, AvantFax, AsteriDex, and Reminders is limited to whitelisted IP addresses. For some implementations, particularly those using Clearly Anywhere, this may not be ideal as UCP can assist with user management of the PBX as well as QR code provisioning of Clearly Anywhere. The Apache web server can be used to manage web access so long as you understand the need to apply Apache security patches in a timely manner.

Assign the same FQDN that you use for SIP access to port 80 for the UCP application. Deploy OpenVPN on your server and use the PBX’s OpenVPN IP address for general access to all web applications we listed above. If you’d like public access to the FreePBX GUI, assign web access for it to another random port, e.g. 8080 in our example below. Block web access to your server from the public IP address of your PBX on both port 80 and 8080 in our example below. Here’s how to accomplish that. Create a new file in /etc/pbx/httpdconf. Create public.conf with the following contents:

Listen 8080

<virtualhost *:80>
ServerAdmin [email protected]
ServerName 111.112.113.114
Redirect 403 /
UseCanonicalName Off
UserDir disabled
</virtualhost>

<virtualhost *:8080>
ServerAdmin [email protected]
ServerName 111.112.113.114
Redirect 403 /
UseCanonicalName Off
UserDir disabled
</virtualhost>

<virtualhost *:80>
ServerAdmin [email protected]
ServerName server-fqdn.com
DocumentRoot /var/www/html/ucp
ErrorLog /var/log/httpd/error_log
CustomLog /var/log/httpd/access_log common
</virtualhost>

<virtualhost *:80>
ServerAdmin [email protected]
ServerName 10.8.0.123
DocumentRoot /var/www/html
ErrorLog /var/log/httpd/error_log
CustomLog /var/log/httpd/access_log common
</virtualhost>

<virtualhost *:8080>
ServerAdmin [email protected]
ServerName server-fqdn.com
DocumentRoot /var/www/html
ErrorLog /var/log/httpd/error_log
CustomLog /var/log/httpd/access_log common
</virtualhost>

<virtualhost 127.0.0.1:80>
ServerAdmin [email protected]
ServerName 127.0.0.1
ServerAlias localhost
DocumentRoot /var/www/html
</virtualhost>

In the ServerAdmin lines, insert your email address. Replace 111.112.113.114 with the public IP address of your server. Replace server-fqdn.com with the FQDN assigned for SIP registration access to your PBX. Replace 10.8.0.123 with the OpenVPN private IP address of your PBX. Replace 8080 with the port you chose for FreePBX access to your server. Save the file and then restart Apache: systemctl restart httpd.

Now it should be safe to open TCP port 80 and 8080 (or whatever port you chose) for web access to your server. Let’s also whitelist TCP 2267 for Clearly Anywhere access while we’re at it:

cd /etc/sysconfig
sed -i 's/10000:20000 -j ACCEPT/&\n-A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT/' iptables
sed -i 's/10000:20000 -j ACCEPT/&\n-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT/' iptables
sed -i 's/10000:20000 -j ACCEPT/&\n-A INPUT -p tcp -m tcp --dport 2267 -j ACCEPT/' iptables
iptables-restart

 

[dhoppy]

@wardmundy , when setting up the VPN server using the article, do I skip the part about using "IPtables to block all server access except via SSH or the VPN tunnel"?

 

[wardmundy]

@wardmundy , when setting up the VPN server using the article, do I skip the part about using "IPtables to block all server access except via SSH or the VPN tunnel"?

We do not recommend setting up OpenVPN server on the same server as Incredible PBX 2020 PUBLIC. If you want to try this, I'd recommend you start with the OpenVPN server install and then add the PUBLIC setup. You may have to tweak the iptables file to be sure UDP 1194 is whitelisted and perhaps adding the POSTROUTING code from the tarball above.

 

[dhoppy]

We do not recommend setting up OpenVPN server on the same server as Incredible PBX 2020 PUBLIC. If you want to try this, I'd recommend you start with the OpenVPN server install and then add the PUBLIC setup. You may have to tweak the iptables file to be sure UDP 1194 is whitelisted and perhaps adding the POSTROUTING code from the tarball above.

Ok, thanks. I misunderstood then.

 

[wardmundy]

We were showing how to deploy and use the OpenVPN Client on PUBLIC, not the OpenVPN Server.

 

[dhoppy]

Vultr to the rescue, I will revert to a snapshot and undo anything I may have broken.

 

[markCFU]

I’ve be using the app about a week now, it’s fantastic!! I can’t get over how little battery drain I get & don’t miss a single call!

The only issue I get is with caller ID, randomly when I call a missed call back in my call history it shows the outbound CID & sometimes when I get an inbound call whilst ringing it shows the caller ID, anyone else?

 

[hbr245b]

I'm a bit late to the game but can Clearly Anywhere be used in conjunction with vanilla asterisk rather than Incredible PBX?

 

[wardmundy]

I'm a bit late to the game but can Clearly Anywhere be used in conjunction with vanilla asterisk rather than Incredible PBX?

If you're using FreePBX.

 

[jerrm]

I'm a bit late to the game but can Clearly Anywhere be used in conjunction with vanilla asterisk rather than Incredible PBX?

If not using FreePBX, then get Acrobits Groundwire from the App/Play Store. It's the same underlying app ClearlyAnywhere and SangomaConnect use without the FreePBX module assisted provisioning.

On Android I also like Grandstream Wave, but lack of push notifications make it problematic on Apple.

 

[hbr245b]

If not using FreePBX, then get Acrobits Groundwire from the App/Play Store. It's the same underlying app ClearlyAnywhere and SangomaConnect use without the FreePBX module assisted provisioning.

On Android I also like Grandstream Wave, but lack of push notifications make it problematic on Apple.

Thank you for the suggestion. I've just bought Groundwire for Android & iPhones to test.