I bought one commercial module : the EndPoint Manager.
I set up my pfSense with option 66 to feed tftp://192.168.1.50 (the IP of my FreePBX server).
I have AASTRA phones, different models, and all of them got provisioned automatically, without any kind of intervention… just resetting to factory default, they upgraded the firmware, and auto configured everything…
And then I have one single GrandStream, a GXP2160.
I don’t understand what to do, I tried everything and it will just not provision itself…
In the end, I just had to set up a SIP account manually from the web GUI.
This really sucks, I actually bought the EndPoint manager because I noticed that the OSS Endpoint Manager didn’t support the GXP2160… It did support all my AASTRA phones though.
Can anyone help? What is the phone looking for when it is booting up? Would it be because it can’t provision from HTTP ? Then what can I do about that ?
I can only confirm what jyates01 has said that the 2160 is supported and works. We have over 600 phones a mixture of GXP2130’s and GXP2160’s and they all provision fine using EPM.
As to what the GXP2160 is looking for when it boots after a factory reset, it simply does a DHCP discovery/request, the DHCP server will give it it’s networking info along with the tftp server address. I use the following in the DHCP config files to distinguish the Grandstreams from other network devices (we have several thousand other devices on this network):-
class “grandstream” {
match if substring (option vendor-class-identifier, 0, 11) = “Grandstream” or
( substring(hardware,1,3) = 00:0b:82 );
option tftp-server-name “172.24.0.1”;
}
The 2160 simply requests its config (cfgxxxxxxxxxxxx, (x’s = mac address in lowercase) file from the tftp server.
I would first check the DHCP log and see that the request is coming into the server and what the reply is. Then check the tftp server logs to see that the 2160 has requested the config file (along with any firmware files etc) and that the file was downloaded.
In our case since the phones are put into a separate VLAN it actually goes through the boot process twice, once to get its VLAN info and then boots again in the VLAN.
To be honest, I skip the reset to factory config setting. I set the firmware and config server to point to the FQDN or IP of my PBX, apply and reboot. First reboot will pick up the new config, and then will reboot again into the new config.
One thing to be aware of with EPM and the Grandstream phones is when ever you update EPM to a new version. Schmooze sometime update their templates for the phones and add extra P values with a default value. If any of these added new P values are the same P number as one you have added yourself to the base template, then this new default value will override your value. I’ve been caught by this a few times. Now I always take a copy of my phones .cfg file (that’s the text version of the config file) and then after updating EPM I regenerate the config for my phone. Then do a diff on the safe config and the new one to see if anything has been added. If it has this will show as a P value appering twice in the new config. If it happens just edit the base template, remove your added P value and change the new added P value to what you want… Its a bit of a pain that new default values override your own values, but at least you can get around it.
The “path” should be a directory path not a network address, the default (empty string) should work fine for tftp (but not necessarily for your chosen http protocol)
It is the path relative your tftpd configured directory usually that is / tftpboot so as i said probably it should be empty if you are using http then relative to your document root usually /var/www/html
Trying to bump this thread as I still haven’t found a working solution.
I’m using the paid version of EndPoint Manager.
I have no idea how to get support from Schmooze : I tried emailing them twice and never got any response.
FreePBX version is: 12.0.74
EndPoint Manager version is: 12.0.0.71
Everything is on latest version as of today.
The problem is simple:
All phones (Mitel, various model) will detect the right provisioning server because I feed them this info from the DHCP server. This one (GrandStream GXP2160) won’t. If i make a factory setting reset, it will just boot with no setting at all.
This sucks but I can live without.
I have replied to your Sales Inquiry form with a copy of the response to your July 9th email. Perhaps you did not see that particular response. Included will be a list of support options available for you.
I have a 2160 on my desk and it provisions just fine via tftp and http. In case it matters, I’m running firmwares: Boot 1.0.1.2, Core 1.0.4.5, Base 1.0.4.18, Prog 1.0.4.23.
On a freshly reset phone, navigate to Maintenance, Upgrade and Provisioning, Select upgrade via tftp, remove the contents of the field Firmware Server Path, Add the PBX IP or FQDN to Config Server Path and leave the rest as default. Save and Apply, and reboot the phone.
Yes some clients don’t like the tftp:// bit, unfortunately some clients won’t work without it, a catch 22 unless you customize your tftpserver (dnsmasq can fix that by serving different parameters for different MAC address masks)
p.s. It doesn’t work with ALL Aastra phones, i.e. 9133’s have exactly that problem.
