We have several SBCs in operation and on each, phones are visible and connect to the PBX without any config changes to the firewalls they live behind.
This one phone, however, will NOT auto-provision to save it's life.
When it appears in the list of phones (listed as "new") it says "192.168.30.17:5080 via SBC 192.168.30.16:5060"... that port (5080) bothers me and I suspect it's the problem.
When I log into the phone itself and check the provisioning tab (grandstream GXP2170), the provisioning link is already set to the correct link (as specified in the extension tab of 3CX management console), but NOTHING else. We waited 24 hours and the phone remained unprovisioned.
I went through and manually updated everything on the phone (sip account, firmware path, and everything else the template should have changed including updating the "proxy" field to point to the SBC on the correct port) and now the phone appears in the phone list as provisioned with no issues. Of course this isn't entirely helpful as the user at that location (the company owner, of course!) would like to use the BLF features... which never update because the phone is not actually downloading the template or updating itself!
I would like to note, that manually provisioning the phone has worked extremely well, the phone is accessible from the users webpanel for call taking, transfers, etc.
Am I right that the port 5080 listed at the start is pointing me in the direction of the issue? Please bear in mind, this is a VERY remote location so I don't have physical access to the phone or sbc.
This one phone, however, will NOT auto-provision to save it's life.
When it appears in the list of phones (listed as "new") it says "192.168.30.17:5080 via SBC 192.168.30.16:5060"... that port (5080) bothers me and I suspect it's the problem.
When I log into the phone itself and check the provisioning tab (grandstream GXP2170), the provisioning link is already set to the correct link (as specified in the extension tab of 3CX management console), but NOTHING else. We waited 24 hours and the phone remained unprovisioned.
I went through and manually updated everything on the phone (sip account, firmware path, and everything else the template should have changed including updating the "proxy" field to point to the SBC on the correct port) and now the phone appears in the phone list as provisioned with no issues. Of course this isn't entirely helpful as the user at that location (the company owner, of course!) would like to use the BLF features... which never update because the phone is not actually downloading the template or updating itself!
I would like to note, that manually provisioning the phone has worked extremely well, the phone is accessible from the users webpanel for call taking, transfers, etc.
Am I right that the port 5080 listed at the start is pointing me in the direction of the issue? Please bear in mind, this is a VERY remote location so I don't have physical access to the phone or sbc.
