Scenario: In this article we will explain the different ways to upgrade your Grandstream device. Supported methods include TFTP, HTTP, HTTPS or File Upload. Upgrade via Grandstream HTTP server: On most Grandstream devices you should find the Firmware Upgrade and Provisioning Settings under the Advanced Settings Page.
Firmware Upgrade and Provisioning: Upgrade Via HTTP Firmware Server Path: firmware.grandstream.com Update Settings and Reboot. Your Grandstream device should now upgrade to the latest firmware listed on the Grandstream Website.
In most cases this will be performed after selecting Reboot (above). DP715 / GXW4xxx / HT50x / HT70x Example: Advanced Settings Firmware Upgrade and Provisioning Settings.
The OnSIP Boot Server serves the latest tested and verified firmware version and user settings for the following models. Supported Grandstream models: DP750, GXP1160, GXP1165, GXP1405, GXP1450, GXP1610, GXP1620, GXP1625, GXP1628, GXP1630, GXP1760, GXP1780, GXP1782, GXP2100, GXP2110, GXP2120,GXP2124, GXP2130, GXP2135, GXP2140, GXP2160,GXP2170, GXP2200, GXV3140, GXV3175, GXV3240, GXV3275, GXW4216, GXW4224, GXW4232, HT502, HT503, HT701, HT702, HT704, HT801, HT802, HT812, HT814 Security Alert Do NOT put phones on static IP addresses directly on the Internet. If you have no other option, you must at least disable port 80 (WWW) inbound to any phone device. If this precaution is not taken, we are not liable for any charges you may incur due to outside access to those phones.
Step 1: Reset your phone to its factory defaults Click the menu button on your phone. In the onscreen menus, select 'Config' (or maybe 'Systems') 'Factory Reset'.
Step 2: Find the Mac Address of your phone and enter it into the OnSIP admin portal You can find your phone's Mac Address printed underneath it. Step 3: Add boot.onsip.com to your Grandstream phone Find the IP address of your phone. In most cases, you should see your phone's IP address on your phone's home screen under Grandstream name. Enter that IP address into your web browser to log in to Grandstream's web-based device configuration tool. The default admin username and password is simply 'admin'. Click on 'Settings' 'Advanced Settings' and scroll down on the page until you see 'Upgrade via'. Make sure that 'http' is checked.
Below that, you should see the field labeled 'Config server path'. Enter 'boot.onsip.com' in this field. Finish it off by scrolling down on the page and clicking the 'Update' button at the bottom. If using Grandstream DP750 or GXP1620 click on 'Maintenance' 'Provisioning' and scroll down on the page until you see 'Upgrade Via' select 'HTTP', in the 'Config Server Path', which is where you would add boot.onsip.com. Save and apply settings. Go to base and restart the base. Remember once the base registers you may need to re-pare the handset. If using Grandstream GXP2100 with version 1.0.5.32 or higher firmware: Click on 'Maintenance' 'Upgrade and Provisioning' and scroll down on the page until you see 'Upgrade Via' select 'HTTP', in the 'Config Server Path' add boot.onsip.com.
Click 'Save and Apply'. Click 'Reboot' and the phone will read the new configuration, connect to the config server and download the new config. While this is happening, it's not apparent that the phone is doing anything (about 2 minutes). Afterwards, your phone will automatically reboot once again before it's ready to be used.
Note: If using the Grandstream GXP2130, GXP2135, GXP2140, GXP2160, GXP2170, if it does not register try the following via the phone menu - System - Upgrade - Start Provision If using Grandstream GXV3240 or GXV3275 select Maintenance Upgrade Config Config Upgrade Via select HTTP from dropdown and then Config Server Path and type in boot.onsip.com. Scroll to bottom of screen and select 'Save'. In upper right in the blue banner select 'Reboot'. This will reboot your phone, which could take upwards of 2-minutes. The phone will then restart on its own and register to OnSIP Boot Server. You will know when it's registered because the User's name will be displayed and there will be a green icon to the left of the name. See all 33 rows on subscene.com. If using Grandstream GXV3240 or GXV3275 with firmware 1.0.3.131, you must turn off the 'Use Grandstream GAPS' option to enter the boot server address.
GWN7600LR
Once you have turned this off, you will see the proper place to enter the 'Config Server Path' as shown below: DHCP Option 66 Disable: In the WWW interface for the phone in the same screen as the Config you should see an option for: 'Allow DHCP Option 43 and Option 66 to Override Server'. Set that to 'No'.
Checking Status: To check too see if the phone is using boot.onsip.com, on the phone itself, choose the home screen and choose the 'System' icon. From there, choose the 'Upgrade' option. There you will see the 'Config Server' settings. To check the local network settings on the phone, on the phone itself, choose the home screen and choose the 'Status' icon. Then choose 'Network Status'.
That will tell you the DHCP information gathered from the phone. Notes. You should not use the boot server if you have multiple VoIP providers configured on your phone, as it provides a minimal configuration for OnSIP service that may cause problems for your other providers. Bluetooth Headsets (as of March 2017): It is not recommended to use Bluetooth headsets with Grandstream model phones, specifically the GXP2170 & GXP2160 (others are also noted in links provided below). The headsets paired with the phones create an audio loop feedback issue that Grandstream is aware but has no resolution as of this update.
If you intend to use a static IP or wish any form of manual configuration for this make of phone, we recommend first provisioning the phone to the boot server then removing the provisioning server before adding your static IP or other manual configurations you need. If you don't remove the boot server, your manual configurations will be overwritten. Revised September 2017 See our top business VoIP phone recommendations for 2017.
We are still seeing about 10% of the Grandstream HT502 adapters that are in use by our customers not properly maintaining their connection to our network and not reconnecting to our network when there is any kind of a short network interruption. With the adapters in question, you've likely had to reboot them when they've lost their connection in order to get them to reconnect to our network so they can receive incoming calls. This is not the way they are supposed to function and they should not need regular reboots. Even when there is a service outage, they should automatically recover from that on their own without you needing to do anything. We've been working with Grandstream to isolate the issue and identify the commonalites in the devices experiencing issues in order to find a fix.
So far, this has been unsuccessful. While the majority of them are maintaining their connection properly, the 10% that are not have created a great deal of problems and made our service seem very unreliable for many of you. Once this issue surfaced, we halted shipments of them and began shipping Linksys PAP2 adapters for new orders. The Linksys devices have been problem-free, stayed connected, and reconnected nearly instantly on their own after outages. In a nutshell, they performed as expected and have allowed us to deliver a reliable service that better resembles the stable service we've delivered over the past two years.
At this point, we are preparing for a potential large-scale recall of the Grandstream HT502 devices exhibiting this behavior. On Thursday, we're going to work with suppliers to determine how quickly we can secure the necessary additional Linksys PAP2 inventory for the replacements and plan out the logistics involved. Our developers will also be working with Grandstream on Thursday to explain that we're about to issue a 'recall' to pull their devices from our network as a last resort to make sure there is nothing else that can be done. If there's not a final 'fix' from Grandstream that we feel comfortable with in place by the end of this week, we'll begin the replacements next week.
While this is a very expensive proposition, I feel it's necessary to restore stability for the customers with the devices in question so they can truly experience VOIPo service. In addition, nearly all our support load is related to this issue so we want to move on and start focusing again on enhancing service for all customers.
Overall, it's just the right thing to do unless by some miracle Grandstream provides us with a fix on Thursday. We want to thank all of you for your patience as we've worked through this and sincerely apologize for any inconvenience it's caused you if you have one of the devices in question. We appreciate your business and continued confident in VOIPo. Expect an update on Friday. Said by: Why not go back to the exact same devices/firmware that you had during this 2 year trouble free beta? They started with the HT286, which was a one port device.
My second service is still using the HT286 without issue. I paid the $29 to get the HT286 for the second line I signed up for. Not long after getting the HT286 the HT502 came out, and then soon after the cloned line.
GWN7600
The cloned line on that one was what I am envious of. One line is so 2003!
My original, most active, HT286 was replaced with HT502, and MWI worked much, much better. MWI functionality and lack of cloned line: would be my main reasons to not go back to the original beta device. Said by: Why not go back to the exact same devices/firmware that you had during this 2 year trouble free beta? They started with the HT286, which was a one port device. You're forgetting the first Zoom 5822 models that failed to make the grade! They were (are?) two line, four account beasts for which they could not get a problem-free firmware in coordination with a manufacturer.
So, I believe they were (justifiably) the first casualties of VOIPo searching for reliability for their customers. Of course, VOIPo's most stable multiple-port test was with their own Courier (temporarily mothballed?) product connected to our asterisk systems! Sorry, just had to let my prejudice show a little bit. At this point, we are preparing for a potential large-scale recall of the Grandstream HT502 devices exhibiting this behaviorI was thinking of the potential of ATA sales, and GrandStream looking like it won't be along long-term (perhaps?) True, but is it really the devices themselves that are failing or is it the set up internally? It seems that Voipo has tried multiple devices over the past 2+ years, and really are having a hard time getting one to be stable for the majority of users. Hopefully the PAP2 is that device. My point is that it has to be something on the Voipo side, not all the devices.
The device manufacturers have plenty of other customers, and I could be a skeptic but I doubt Voipo is considered a major player in the voip market yet. Said by ptrowski True, but is it really the devices themselves that are failing or is it the set up internally?
It seems that Voipo has tried multiple devices over the past 2+ years, and really are having a hard time getting one to be stable for the majority of users. Hopefully the PAP2 is that device. My point is that it has to be something on the Voipo side, not all the devices. The device manufacturers have plenty of other customers, and I could be a skeptic but I doubt Voipo is considered a major player in the voip market yet. I was originally leaning towards it being on our end, but it doesn't make sense that you can have two of them side by side configured exactly the same and one consistently gives out 'Seg Fault' errors and crashes. Every time someone fails to re-connect, they device has 'Seg Faulted'. I could be wrong, but there are two key points here that reinforce my opinion that some of these devices have a defect now.
First, why would some HT502s be crashing on their own consistently while others never do when they're configured the same way and used behind the same network. Second, why would some of them work perfectly fine on our network and then suddenly start having these issues after the firmware upgrade even if we downgrade them back to the old firmware. We made no major changes on our end between then. Said by ptrowski True, but is it really the devices themselves that are failing or is it the set up internally? It seems that Voipo has tried multiple devices over the past 2+ years, and really are having a hard time getting one to be stable for the majority of users. Hopefully the PAP2 is that device. My point is that it has to be something on the Voipo side, not all the devices.
The device manufacturers have plenty of other customers, and I could be a skeptic but I doubt Voipo is considered a major player in the voip market yet. I was originally leaning towards it being on our end, but it doesn't make sense that you can have two of them side by side configured exactly the same and one consistently gives out 'Seg Fault' errors and crashes. Every time someone fails to re-connect, they device has 'Seg Faulted'. I could be wrong, but why would some HT502s be crashing on their own consistently while others never do when they're configured the same way and used behind the same network. To beat ptrowski to the punch- You make a good point, but what about three different services running in parallel, with one service having troubles with 10% of its customers, but the other two services not having 'widespread' issues with the 502?
- IMO, the issue is more complex than simply assigning cause to the provider OR to the device. Also, I recall some question earlier about downgrading firmware and Tim not wanting to do so en masse. Have your affected GS502 customers been offered the f/w downgrade to see if this would resolve the issue? Said by Fisamo Also, I recall some question earlier about downgrading firmware and Tim not wanting to do so en masse. Have your affected GS502 customers been offered the f/w downgrade to see if this would resolve the issue?
We haven't done it for everyone but have tried it in individual cases without success. Trust me, we'd rather not incur the cost of replacing all these, but ultimately some of these devices are causing serious issues that in every case we've tried have been cleared up immediately by using another device such as a PAP2T or a Grandstream Handytone 286. Still though, a device should never just start giving out 'Seg Fault' errors when it's just idle. The HT502 is their newest one and apparently needs more time to mature. If you look back at the history of GS's other devices, quite a few 'losing registration' issues came up with them in their early years as well. Said by: The HT502 is their newest one and apparently needs more time to mature.
If you look back at the history of GS's other devices, quite a few 'losing registration' issues came up with them in their early years as well.I think Grand Stream as a whole needs to mature. When I tried talking to them I didn't like the vibe I was getting, and we went with PAP2's and SPA's instead. In retrospect, I'm glad we did.
We haven't had a single issue like everything you're experiencing in over a year. Will GS let you return the devices en-masse? I'd hope so given they can't get them to stay up, but it's been a while so they might give you the legal reach around. Said by nitzan Will GS let you return the devices en-masse? I'd hope so given they can't get them to stay up, but it's been a while so they might give you the legal reach around. I'm sure they won't accept them as returns without a fight, but I haven't really even gotten into that with them at this point. Our first priority is to stabilize things for customers.
Then we'll do with the financial aspects of it like that behind the scenes. I'm sure there is eventually going to be something that can be done to fix them, so ultimately they can likely be re-used later after things have stabilized, but for now we need to focus on the immediate situation. Said by: I took it as plural, not possessive.
(502s) EDIT: Or were you asking Tim if HT502 was 1 in 10 failed. Likely 1 in 10 sent back of a 1000 or more sent out maybe? I guess I may have read it wrong, but it seemed that Tim always observed a 1 out of 10 failure rate with the GS HT502 adapters.
My question would be is when was this first observed? When sent to Voipo? Wouldn't that be a cause for concern as to not use them in the first place if they observed a 10% DOA rate from the manufacturer?
Grandstream HandyTone 502 with sipXecs The offers links to the respective user manuals for the different models. Note: By default the HandyTone terminal adaptors are configured to receive firmware upgrades from Grandstream's HTTP server at fm.grandstream.com/gs. This means that when you first plug in your new HandyTone TA and there is connectivity to the Internet, it will upgrade its firmware if a newer version is available. Do not disconnect power until completed. Grandstream HT502 Handytone 502 Configuration. Plug an analog telephone into the PHONE1 port.
Plug the Ethernet cable into the WAN port of the Grandstream HT502 in order to connect it to a router or an Internet connection. Connect the power cord to the Grandstream HT502. Connect an Ethernet cable from a PC to the LAN port of the HT502.
Verify that the PC obtains a valid IP address from the Grandstream HT502. Make sure that the PC's Ethernet adapter is set to 'Obtain an IP address automatically'. Because HT502 provides a DHCP server and enable DHCP in the default setting, the PC can obtain an IP address from the HT502. Run 'ipconfig /renew' in the DOS command mode on the PC. By this command, the PC will obtain an IP address.
If the PC obtains an IP address, exp. 192.168.2.100 and the default gateway is 192.168.2.1, Then, the PC can access the Grandstream HT502 by 192.168.2.1. (WAN sited HTTP accesss is disabled by default, initial access is always from the LAN port). Enter default password of: 'admin'. Under Advanded Settings, set Firmware Upgrade Type to: TFTP, Firmware Server Path: server/gs and Config Server Path: set to 'yourSIPserver'.
From the sipX ConfigServer administration portal:. First add a New User for every FXS line supported by the HandyTone terminal adaptor. Add a New Phone and select the Grandstream HandyTone terminal adaptor from the drop-down menu. Note: Version 4.2.1 doesn't have a Handytone 502 template so select model 486. Enter the proper MAC address. Assign a line to the terminal adaptor by selecting the appropriate user.
Enter correct Time Zone under Phone, Apply. Under Network, check WAN Side HTTP Access and Reply to ICMP on WAN port. Layer 2 VLAN is set to 20 and Layer 2 QoS is set to 6 and 802.1p priority value set to: 0. Under Upgrade, set Firmware Upgrade Type to: TFTP Upgrade, Firmware Server Path: server/gs and Config Server Path: set to SIPserver. Check Automatic TFTP/HTTP Upgrade, Apply. Generate profiles (configuration files for the terminal adaptor) and reboot the adapter. Default parameters should result in a working setup.
Sonma Typing-Expert, free and safe download. Sonma Typing-Expert latest version: Free Hindi/English software to improve typing fluency. Sonma Typing-Expert is the app for Hindi/English speakers who wish to improve their typing fluenc. Hindi typing tutor download for windows 7.
From within ConfigServer you can change parameters later and re-generate the profile. The terminal adaptor should now pick up the profile generated by ConfigServer and register with sipX. Note: Automated restart of the terminal adaptor from ConfigServer will not work yet even once the terminal adaptor registered successfully. Factory Reset If you screw up and need to reset back to default factory settings (with reset button).
Unplug the Ethernet cable. Locate the needle-sized hole on the back panel of the gateway, next to the power. Insert a pin in this hole, and press for about 7 seconds. Take the pin out. All unit settings are restored to factory settings.