3CX hosted on Amazon Lightesail - Registering phone issue

Forums › VoIP › 3CX hosted on Amazon Lightesail - Registering phone issue

SATTV

1648 posts

Uber Geek

ID Verified

#246707 18-Feb-2019 14:29

Hi All,

I have set up 3CX on a Amazon Lightesail VM and have the PBX largely configured.

The issue I am having is registering phones, I have set up a Session Boarder Controller using a Raspberry Pi.

The instructions say that you can just restart the phones and they will show in 3cx console --> Phones ready to be assigned to an extension.

When I have done this I can not see any phones that were on our network, thinking I might have stuffed up I have reinstalled the software on the Pi but there has been no change.

I have turned off the Pi and installed the SBC on my desktop but same result ( I copied the SBC password so it should not be a password issue )

Can someone please let me know if this is or is not the case, It is a shame there is no indication on the 3CX console that the SBC is up and working, this has been a feature request for years from what I have found online.

I am trying to provision phones by the weblink but this has mixed results.

The phones I have with the PBX are

Yealink T27P ( working )

Yealink T26P ( Not working )

SNOM 320 ( not working )

While these phones are not offically supported as they are on the end of life list they are on the list of supported phones.

I was under the impression that with a SBC the provisioned and unprovisioned phones will show in the phones tab.

In the profile extn: options

Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked) is unticked.

Thanks in advance.

John

I know enough to be dangerous

chevrolux

4962 posts

Uber Geek
Inactive user

#2182029 18-Feb-2019 15:12

I don't use SBC very often, but when I do, I use option 66 provisioning.

Set your given provisioning URL in your DHCP server for option 66. Set up the phones in each extension (enter MAC, set as "Remote SBC"), and then just reboot the phone and wait for provisioning to happen. During that process you will be prompted to enter a username/password which is just your extension number and the voicemail PIN.

My preferred for remote phones on 3CX is just direct remote phones. Supported phones use RPS, so just set the phone up, plug it in and it's working in a few minutes.

SATTV

1648 posts

Uber Geek

ID Verified

#2182103 18-Feb-2019 17:06

chevrolux:

I don't use SBC very often, but when I do, I use option 66 provisioning.

Set your given provisioning URL in your DHCP server for option 66. Set up the phones in each extension (enter MAC, set as "Remote SBC"), and then just reboot the phone and wait for provisioning to happen. During that process you will be prompted to enter a username/password which is just your extension number and the voicemail PIN.

My preferred for remote phones on 3CX is just direct remote phones. Supported phones use RPS, so just set the phone up, plug it in and it's working in a few minutes.

Thanks for the reply.

I have put the prov code in Option 66.

I reset the phone and expected it to provision but alas same issue.

I am prompted for a account & registrar but that does not seem to do anything ( I have tried extension + pin & extenson@fqdn ) even a manual autoprovision code is not working, I can manully set up the phone but this is not what I want to do.

I will install a SBC at home tonight to see how that performs.

John

I know enough to be dangerous

coffeebaron

6231 posts

Uber Geek

Trusted

Lifetime subscriber

#2182104 18-Feb-2019 17:12

I take it you've checked open ports - i.e. 5090/5000/5001 all open?

Rural IT and Broadband support.

Broadband troubleshooting and master filter installs.
Starlink installer - one month free: https://www.starlink.com/?referral=RC-32845-88860-71
Wi-Fi and networking
Cel-Fi supply and installer - boost your mobile phone coverage legally

Need help in Auckland, Waikato or BoP? Click my email button, or email me direct: [my user name] at geekzonemail dot com

SATTV

1648 posts

Uber Geek

ID Verified

#2182207 18-Feb-2019 19:18

coffeebaron:

I take it you've checked open ports - i.e. 5090/5000/5001 all open?

The windows firewall has a rule for the 3cxsbc so it should just work. It should only need 5060 as that is what it is translating to 5090 over the tunnel. Disabling the firewall does not help.

I installed the SBC software on my home computer and my test phone shows in the phones which is good but I still can not get it to provision which is a pain.

John

I know enough to be dangerous

chevrolux

4962 posts

Uber Geek
Inactive user

#2182221 18-Feb-2019 19:48

The SBC uses 5090 to create the tunnel first so you must have that port open. But you should only need that open on the server side as connections are initiated from the SBC software.

Just tested here at home to our office server (v16 beta)... (firstly removed option 66 just to test in a "plain" environment)

- Ran up SBC software on linux VM - used standard wizard presented during install to configure.
- Plugged in phone on remote LAN (default Fanvil X5)
- Phone automatically came up in "phones" tab as a new phone available to provision (this surprised me majorly. I was always under the impression option 66 was required when the phone wasn't on the same layer 2 network as 3CX). The "IP" in the phones tab is presented as "192.168.10.59:5060 via SBC 192.168.10.75:5060" with .59 being the phone and .75 being the SBC.
- Selected phone, clicked "Assign Ext" and assigned it to my chosen extension. One thing I noted at this point is the "3CX Session Border Controller" option in the provisioning tab was the private IP address of the SBC and not the public of my home network.
- Clicked OK, phone auto-provisioned.

So zero touch on the phone, and apparently no requirement for option 66. I would say if it's not working on a particular handset, factory default and manually upgrade the firmware to the latest. I had some issue with some old Fanvil firmware - similar issue as you have where it just won't play the game with 3CX auto-provisioning.

If one phone has registered and is "via SBC" (look in the phones tab) that tells you at least the tunnel is up.

SATTV

1648 posts

Uber Geek

ID Verified

#2183223 18-Feb-2019 20:18

chevrolux:

The SBC uses 5090 to create the tunnel first so you must have that port open. But you should only need that open on the server side as connections are initiated from the SBC software.

Just tested here at home to our office server (v16 beta)... (firstly removed option 66 just to test in a "plain" environment)

- Ran up SBC software on linux VM - used standard wizard presented during install to configure.
- Plugged in phone on remote LAN (default Fanvil X5)
- Phone automatically came up in "phones" tab as a new phone available to provision (this surprised me majorly. I was always under the impression option 66 was required when the phone wasn't on the same layer 2 network as 3CX). The "IP" in the phones tab is presented as "192.168.10.59:5060 via SBC 192.168.10.75:5060" with .59 being the phone and .75 being the SBC.
- Selected phone, clicked "Assign Ext" and assigned it to my chosen extension. One thing I noted at this point is the "3CX Session Border Controller" option in the provisioning tab was the private IP address of the SBC and not the public of my home network.
- Clicked OK, phone auto-provisioned.

So zero touch on the phone, and apparently no requirement for option 66. I would say if it's not working on a particular handset, factory default and manually upgrade the firmware to the latest. I had some issue with some old Fanvil firmware - similar issue as you have where it just won't play the game with 3CX auto-provisioning.

If one phone has registered and is "via SBC" (look in the phones tab) that tells you at least the tunnel is up.

Thanks for testing that out for me, I have done the same ( except windows ) I click ok but the phone ( Yealink T26P ) does not provision.

The phones have been upgraded to the latest firmware already and factory reset a number of times.

I am starting to think the later versions of 3cx do not like slightly older phones

John

I know enough to be dangerous

chevrolux

4962 posts

Uber Geek
Inactive user

#2183233 18-Feb-2019 20:33

Yea that's quite strange. So it finds the unprovisioned phone no problem, but then just wont provision after assigning an extension?

Those phones are still on the supported list (even on v16 beta), so you would assume they should be fine.

Have you got a paid license (or a resller)? If so, download the support info and flick it through to 3cx support.