Any Azure experts on here?

[hogan71088]

Hi All,

I have been doing some testing with PBXexpress and Azure which has been going well. I have setup a site to site VPN between our office and Azure which has connected fine. I can ping the internal IP address of the 3CX Azure instance which replies perfectly.

First issue was when I tried to provision a Yealink phone, I tried to provision it manually without success so I tried accessing the 3CX instance through the internal IP address over the site to site VPN. It seems like it is trying to load the page but it eventually fails.

Maybe there's something simple I'm missing?

 

[Saqqara]

Can you access the 3CX management console, externally from another WAN IP address ?

Are you trying to access the server via IP address or FQDN , also make sure you add the correct port to the url

As for setting up the phones

if you have a site to site vpn and all ports are open - provision the phones via 3CX

You need to setup dhcp option 66 on the remote end (where the phone are based)
https://www.3cx.com/sip-phones/dhcp-option-66/

Depending on the phone, configure the phone as local lan -
https://www.3cx.com/sip-phones/

 

[hogan71088]

Hi Saqqara,

I can access the management console from the FQDN and the public IP address. I'm trying to access it through the internal IP address over the VPN, I can ping the network card of the virtual machine over the VPN but it doesn't seem to load in a browser.

 

[cobaltit]

Are you trying to acess via http or https? And are you using the correct port?

 

[CentrexJ]

What device is your local firewall? Perhaps not all services are opened in the access rules?

 

[hogan71088]

The firewall we're using is Meraki, we've setup the VM on Azure using PBXexpress, I've tried accessing the management console through ports 5001, 443 and also without any port just using the internal IP address.

 

[CentrexJ]

The firewall we're using is Meraki, we've setup the VM on Azure using PBXexpress, I've tried accessing the management console through ports 5001, 443 and also without any port just using the internal IP address.

In portal.azure.com, did you shrink the pbxexpress subnet on the virtual network and then add a gateway subnet? We found that pbxexpress on azure created a subnet that used the entire virtual network which left no room for the gateway subnet. We had to first reduce the size of the subnet that 3cx created to do so.

Once setup correctly, the phones on the office side provision as local phones as if the pbx was on-prem. e.g. http://10.0.0.4/provisioning/randompath - as you can see this uses port 80. You can use DHCP 66 pointing there as well.

 

[hogan71088]

In portal.azure.com, did you shrink the pbxexpress subnet on the virtual network and then add a gateway subnet? We found that pbxexpress on azure created a subnet that used the entire virtual network which left no room for the gateway subnet. We had to first reduce the size of the subnet that 3cx created to do so.

Once setup correctly, the phones on the office side provision as local phones as if the pbx was on-prem. e.g. http://10.0.0.4/provisioning/randompath - as you can see this uses port 80. You can use DHCP 66 pointing there as well.

Yes exactly, I actually changed the address space from a 10.0.0.0/16 to a 192.168.0.0/24 range, created a 192.168.0.0/25 subnet and then added a GatewaySubnet in that range also.

The strange thing is, when I put the internal IP address of the VM into a browser, I can see it's trying to open the page, in the tab on the browser it says '3CX Phone System Management Console' but just spins around. If I put the internal IP in the browser with the port:443 I get a bad request 400 response.

 

[CentrexJ]

The Gateway subnet needs to be a separate subnet in the virtual network. If your pbx and gateway are both in the 192.168.0.0/25 subnet that that's likely why it doesn't work. You may have done that as well it's hard to tell from your description.

Perhaps because you changed the local IP of the pbx it broke something?

Here's how I do it and the 3CX pbxexpress local IP doesn't have to change:
Virtual Network 10.0.0.0/16
3CX Subnet 10.0.0.0/24
Gateway Subnet 10.0.1.0/27

 

[hogan71088]

The Gateway subnet needs to be a separate subnet in the virtual network. If your pbx and gateway are both in the 192.168.0.0/25 subnet that that's likely why it doesn't work. You may have done that as well it's hard to tell from your description.

Perhaps because you changed the local IP of the pbx it broke something?

Here's how I do it and the 3CX pbxexpress local IP doesn't have to change:
Virtual Network 10.0.0.0/16
3CX Subnet 10.0.0.0/24
Gateway Subnet 10.0.1.0/27

To clarify the Gateway Subnet is in a /28 so all good. I think you're probably right, I'd say changing the local IP might have broken something. Trying to figure out with Wireshark, cheers for the responses.