Solved Provisioning link does not seem to work on 3CX - Pi

[mcteck]

I have an issue that I just cannot crack...I recently installed 3cx on a recent install...

Everything else seems to work well - soft phones work, can make calls out, etc.. When I attempt to provision my Yealink T46s through 3cx - nothing happens. Next, I manually entered the provisioning URL (http://IPaddress:5000/provisioning/etc) into the phone embedded web page - still nothing. If I change the URL to the secure version (https, change 5000 to 5001), the phone provisions...then reboots and reverts to the 5000 again and will not function. Why is the standard link failing? Everything is local...seems I cannot get to the provisioning link for some reason. The issue sounds identical to this previous thread (which has been closed).

https://www.3cx.com/community/threa...-from-the-local-ip-403-forbidden-nginx.76654/

My specifics:

• 3CX Version - Standard Annual 18.0.237
• Server OS - Raspberry Pi - Raspbian GNU/Linux 10
• Yealink T46S version 66.86.0.1
  
• Provisioning Method: Local
• Trunk Provider or VoIP Gateway Make/Model, Skyetel
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

I appreciate any help you can provide. Thx...

 

[ClaudioBassani]

Hy
try resetting the phone to factory default and install the 3CX recommended firmware (66.86.0.5)
https://www.3cx.com/support/phone-firmwares/
Check that the network has allowed addressing in one of the following classes

• Class A networks use a default subnet mask of 255.0.0.0 and have 0-127 as their first octet. The address 10.52.36.11 is a class A address. Its first octet is 10, which is between 1 and 126, inclusive.
• Class B networks use a default subnet mask of 255.255.0.0 and have 128-191 as their first octet. The address 172.16.52.63 is a class B address. Its first octet is 172, which is between 128 and 191, inclusive.
• Class C networks use a default subnet mask of 255.255.255.0 and have 192-223 as their first octet. The address 192.168.123.132 is a class C address. Its first octet is 192, which is between 192 and 223, inclusive.

Also check: Dashboard->Security->Secure SIP

 

[Saqqara]

What is your internal IP address range ?

Have you been able to provision any other phones

Being internal, the url will be http

 

[mcteck]

Hy
try resetting the phone to factory default and install the 3CX recommended firmware (66.86.0.5)
https://www.3cx.com/support/phone-firmwares/
Check that the network has allowed addressing in one of the following classes

• Class A networks use a default subnet mask of 255.0.0.0 and have 0-127 as their first octet. The address 10.52.36.11 is a class A address. Its first octet is 10, which is between 1 and 126, inclusive.
• Class B networks use a default subnet mask of 255.255.0.0 and have 128-191 as their first octet. The address 172.16.52.63 is a class B address. Its first octet is 172, which is between 128 and 191, inclusive.
• Class C networks use a default subnet mask of 255.255.255.0 and have 192-223 as their first octet. The address 192.168.123.132 is a class C address. Its first octet is 192, which is between 192 and 223, inclusive.

Also check: Dashboard->Security->Secure SIP
View attachment 25563

I have switched to the recommended firmware multiple times - just tried again...same behavior. I am using a Class C address. My Pi is on 192.22.80.111 - the phone is 192.22.80.196. I have no issues using the embedded web server from the devices but provisioning just doesn't happen without switching to 5001.

 

[mcteck]

What is your internal IP address range ?

Have you been able to provision any other phones

Being internal, the url will be http

I am using 192.22.80.1-255. Both devices are in that range. I have not used any other phones (other than successfully using the app). I do have another T46s but I haven't pulled it out of the box yet. I fully expected the http URL to work but it just doesn't - I'm baffled.

 

[SweetAction]

192.22.x.x(/16) is not in RFC1918 space - that's a public IP range.

This install of 3CX is configured that all devices appear to be on WAN
https://www.3cx.com/blog/docs/network-topology/

 

[Saqqara]

As above you are not using a rfc 1918 address https://www.dummies.com/programming/networking/private-ip-address-ranges-for-networks/

You need to change your Lan ip address range to rfc 1918 address, probably configured on your router. When you have done this reinstall 3cx on pi

 

[mcteck]

As above you are not using a rfc 1918 address https://www.dummies.com/programming/networking/private-ip-address-ranges-for-networks/

You need to change your Lan ip address range to rfc 1918 address, probably configured on your router. When you have done this reinstall 3cx on pi

I now see in the docs how 3CX will assume these are on WAN based on the range....that is what I was not getting.
Thanks.

 

[mcteck]

192.22.x.x(/16) is not in RFC1918 space - that's a public IP range.
View attachment 25566
This install of 3CX is configured that all devices appear to be on WAN
https://www.3cx.com/blog/docs/network-topology/

Ok, I understand...knew the situation with the network, but didn't know 3CX would assume those were WAN devices based on the range...Thx.

 

[ChrisC_3CX]

As the cause of the issue has been identified, I will be marking this thread as solved. Please do not hesitate to start a new thread should anything else come up.