Cannot Get Cisco 525g2s to provision on local network

[ricksimnett]

Hello,
We are setting up a 3cx pbx on a local network running in a vm. The pbx itself seems to be functional, and we have successfully linked to our sip trunks and all that working.

The challenge we are facing is getting our legacy cisco 525g2s to provision against the local 3cx install.

The 3cx instlal has a static ip, and is pingable from everywhere on our network. There is no firewall blocking anything (we disabled it as a measure of testing).

We have followed the guides related to this online. Specifically the phones have been factory reset, and then we have fed them the provisioning resync url. The phones never restart, and never successfully provision.

As I was going through the various scenarios I started focusing on the provisioning URL itself. http://x.x.x.x/provisioning/... when I hit the url given to me by the 3cx pbx - all I get in a web browser is 403 Forbidden - not the expected xml output.

If I access the 3cx pbx using the fqdn http://..../provisioning/.... - I get a different message about
This site can’t provide a secure connection

I have inspected the nginx config on the server, and as its configured I get the 403 error because I am specifying only the ip not the domain name. When I use the domain I get the other response.

Can anyone tell me where I am going wrong in all of this? It seems fairly straight forward - yet I somehow cant seem to figure out why I cant get a response out of the server.

Thank you in advance for any help you can lend.

 

[Saqqara]

Have you followed https://www.3cx.com/Sip-Phones/Cisco-SPA/

I would pay attention to extra requirements in step 1

 

[the_jackal_br2001]

Hi @ricksimnett

Try to use the specific firmware version from 3CX docs as mentioned in last post.
Version is Cisco SPA 525G - Firmware 7.6.1

 

[leejor]

Those sets have a very easy to navigate GUI, you might try manually setting up one line and see how it goes.

 

[ricksimnett]

Have you followed https://www.3cx.com/Sip-Phones/Cisco-SPA/

I would pay attention to extra requirements in step 1

Yes I did actually - I tried this with 2 firmware versions. 7.6.2 is what I started with (this was on the phone I tested with by default). I also tried downgrading the firmware to 7.6.1 and that didnt seem to do it either. I did also copy the zip files into (we run the debian distro) - /var/lib/3cxpbx/Http/Data/provsubdir (this was the closest directory I could find in relation to the Windows path given in the document).

 

[ricksimnett]

Hi @ricksimnett

Try to use the specific firmware version from 3CX docs as mentioned in last post.
Version is Cisco SPA 525G - Firmware 7.6.1

Yes. I did try this. No dice. Granted I'm not 100% sure I put the files in the right directory on the debian 3cx (but I think I did). I also just tried applying the firmware update of the version directly, and then tried the provisioning procedure - that didnt work either.

 

[ricksimnett]

Those sets have a very easy to navigate GUI, you might try manually setting up one line and see how it goes.

Hmmmm... so I can just set the proxy to the PBX, auth id and password and connect? will all the phone functionalities covered by the auto provisioning still work? IE. call transfer, voicemail, etc?

 

[JohnS_3CX]

@ricksimnett

Follow the guide we provide, if need be start from scratch: https://www.3cx.com/Sip-Phones/Cisco-SPA/

The support files will need to be extracted here for Debian:

/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/XXXXXX/

Ensure the DHCP Options are set correctly. Check there are no other DHCP options that may conflict according to phone manufacturer (like 150,160 perhaps) and that there is no other network equipment that would take precedence (ie. some Cisco equipment that can configure phones)

The provisioning folder is not accessible to you neither locally nor from the internet. The phone though will know how to access it when you set it up as per the guide and if you set up the correct mac address in the extension provisioning.

 

[ricksimnett]

@ricksimnett

Follow the guide we provide, if need be start from scratch: https://www.3cx.com/Sip-Phones/Cisco-SPA/

The support files will need to be extracted here for Debian:

/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/XXXXXX/

Ensure the DHCP Options are set correctly. Check there are no other DHCP options that may conflict according to phone manufacturer (like 150,160 perhaps) and that there is no other network equipment that would take precedence (ie. some Cisco equipment that can configure phones)

The provisioning folder is not accessible to you neither locally nor from the internet. The phone though will know how to access it when you set it up as per the guide and if you set up the correct mac address in the extension provisioning.

Thanks for the additional info John. Ill give it another shot and report back.

 

[ricksimnett]

@ricksimnett

Follow the guide we provide, if need be start from scratch: https://www.3cx.com/Sip-Phones/Cisco-SPA/

The support files will need to be extracted here for Debian:

/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/XXXXXX/

Ensure the DHCP Options are set correctly. Check there are no other DHCP options that may conflict according to phone manufacturer (like 150,160 perhaps) and that there is no other network equipment that would take precedence (ie. some Cisco equipment that can configure phones)

The provisioning folder is not accessible to you neither locally nor from the internet. The phone though will know how to access it when you set it up as per the guide and if you set up the correct mac address in the extension provisioning.

Hi John - still not working - I literally redid every step and still cant get the phones to provision locally. There are 16 in total - I cant get one to connect.

I also tried to manually configure the device. I tried to setup 1 line on the phone to connect to the PBX as the Proxy. I placed the ID and password in the Auth_ID and Passowrd fields (and later on the User ID field as well) in the phones configuration - much like I did when we were running asterisk - and I get a 404 error back on the phone when it tries to connect.

Is there somewhere in 3cx where I can view the registration logs? I guess I need to understand why I cant even manually connect a phone just as a manually configured SIP device.

 

[leejor]

Is there somewhere in 3cx where I can view the registration logs? I guess I need to understand why I cant even manually connect a phone just as a manually configured SIP device.

Check the 3CX Activity Log. That will show you if there is even a registrarion attempt.

 

[ricksimnett]

Check the 3CX Activity Log. That will show you if there is even a registrarion attempt.

Ah! I didnt realize the dashboard gave you that kind of info. I purged rebooted the phone, saw Block on Wan Error - adjusted the extension and the phone connected. Thanks for your help. I can manually configure and register a phone now.

Any idea if that same setting would block the auto provisioning?

 

[cobaltit]

If it's a block on wan error then the phones aren't local. Something isn't right with your configuration

 

[leejor]

In the phone's settings, are you using the private IP of the 3CX server, or the FQDN with no local DNS resolution?

 

[JohnS_3CX]

Hi Rick,

Indeed, as per the guide these phones are not supported in STUN or SBC mode, only local.

When we say "local" phones we mean phones that are in the same subnet as the PBX such that they appear as local peers which can use a provisioning URL that is in the same subnet as the PBX.

You must be using the LAN interface as opposed to the FQDN (otherwise they will fail firstly due to not TLS support before anything else) or you might have future issues with calls.

So if you are being blocked by WAN the question arises of where are the phones installed in relation to the PBX? Why are they reaching the PBX via WAN?