Grandstream HT802v2 (General) Device Config

[tanny]

I recently upgraded my VoIP/ATA from a Linksys SPA-2102 to -> Grandstream HT802v2 because I've been having problems with my old SPA-2102 not registering because it can't support any alternate SIP server "failover" options. -see here: viewtopic.php?p=82696#p82696

(In Canada, I actually got a good deal purchasing a new HT802v2 from https://voicedepot.ca/products/grandstr ... xs-adapter
and no, I'm not trying to solicit for anyone, 'jus sayin').

Anyway, So far so good, and I'd just like to mention that the HT802v2 is working very well, and fairly simple to setup, thanks to the general (device configuration) guide here:
https://support.freephoneline.ca/hc/en- ... redentials
As well as the more (newer) detailed guides and feedback from these threads:
HT802 Device Config -> viewtopic.php?t=20252
HT812 Device Config -> viewtopic.php?t=20943

Without this Freephoneline Forum, I'd be lost, so mucho thanks to all for all your contributions.

[Liptonbrisk]

I've been having problems with my old SPA-2102 not registering because it can't support any alternate SIP server "failover" options

The reason the SPA2102 wasn't registering was due to voip.freephoneline.ca not accepting registration requests on October 5th, and then voip2.freephoneline.ca experienced the same problem on October 8th. Those were problems that Fongo has since resolved. So, your SPA2102 should still work. It just lacks the ability to automatically switch (failover) to another server when the proxy or SIP server fails to respond.

I'm glad you were able to configure your new ATA successfully.

I would strongly encourage you to follow these instructions as well if you haven't already: viewtopic.php?t=20961.

[tanny]

I've been having problems with my old SPA-2102 not registering because it can't support any alternate SIP server "failover" options

The reason it wasn't registering was due to voip.freephoneline.ca not accepting registration requests on October 5th, and then voip2.freephoneline.ca experienced the same problem on October 8th. That was a problem that Fongo has since resolved.

I'm glad you were able to configure your new ATA successfully.

I would strongly encourage you to follow these instructions as well if you haven't already: viewtopic.php?t=20961.

Yes, but that's not the first time that this has happened with our spa-2102, that said, our old spa-2102 has been fairly rock solid for almost 15 years so I have no complaints about it. -It'll be my backup in any case.

Now that I've tested/registered my new HT802v2 with (freephoneline) and basic registering/calling out/in as well as some banking option calls with no issues, I'll also setup SIP server failover options as you've recommended in your link.

One thing I've noticed with a hard network reboot, is that the HT802v2 comes up almost as fast as my Router now, whereas the spa-2102 would take an extra 2-3 minutes or so to fully register/connect.

Also, on a side note, regarding the HT802v2, I've tried to save the entire Device Configuration from the "Download" option but all it does is store it in some "si" file, -"si" being a "system information" file without a file extension?, except that's it's basically unreadable and I can't seem to save it into a "pdf" or "jpg" inage file, ... ?
The "xml" file from another optional export setting simply exports it to a very long list of alphanumeric numbers that don't really mean anything.?

Other than that, it's smooth sailing, but if anyone has any ideas on how to download a complete/readable config file, (convertible to a pdf or jpg), for the HT802v2 than please let me know.

[Liptonbrisk]

that said, our old spa-2102 has been fairly rock solid for almost 15 years so I have no complaints about it. -It'll be my backup in any case.

Good idea

One thing I've noticed with a hard network reboot, is that the HT802v2 comes up almost as fast as my Router now, whereas the spa-2102 would take an extra 3 minutes or so to fully register/connect.

Okay, please keep the following in mind.

This is always proper device reboot order:

A.Turn off modem, router, and ATA (or IP Phone or close SIP App).

B. Turn on modem. Wait for modem to be fully up and running.

C.Turn on router.
Wait for modem to be fully up and transmitting data before turning on router.

D. Turn on ATA (or IP Phone or open SIP app) only after the router is fully up and running.

The SIP device or client (ATA, IP Phone, or SIP app) should be the last device powered on in the device chain.

Some people don't have a separate modem and router (they have, instead, a modem/router combo, Rogers Gateway, Bell Hub, or Telus Hub, for example, which are all modem/router combos). Regardless, the ATA should be booted last after everything else is fully up and running first. The reason for that is explained in point D from viewtopic.php?p=78976#p78976 (I appreciate that not everyone can afford a separate router and that the instructions may seem daunting). Unless UDP timeouts can be adjusted properly in a router, the ATA should be booted last in the device chain, including after power outages (a UPS is a good idea).

[tanny]

...
Unless UDP timeouts can be adjusted properly in a router, the ATA should be booted last in the device chain, including after power outages (a UPS is a good idea).

Agreed, but even when either one is booted last as I've tested in my home system, the HT802v2 registers/connects in ~15 secs, whereas my old SPA-2102 took about 2-3 minutes, it's just a point of fact, and not an opinion.
The fact that the spa-2102 is also a "Router" may also play into that.?

[Liptonbrisk]

...
Unless UDP timeouts can be adjusted properly in a router, the ATA should be booted last in the device chain, including after power outages (a UPS is a good idea).

Agreed, but even when either one is booted last as I've tested in my home system, the HT802v2 registers/connects in ~15 secs, whereas my old SPA-2102 took about 2-3 minutes, it's just a point of fact, and not an opinion.

I wasn't disputing that. The point I'm making is that depending on your devices, it's important to boot your ATA last, especially because your new one appears to boot faster. Consider what happens to people when power is restored after power outages. Suddenly all devices power back on at the same time. Since your SPA2102 is slow to boot and register, it's possible your modem, router, and SPA2102 ATA booting simultaneously never mattered; the ATA may have booted up last regardless (a scenario where the ATA fails to register based on device boot order may not apply to you, depending on UDP default settings in your devices).

However, your new ATA boots faster, so this scenario I'm describing where an ATA may now boot up before it has internet (WAN) access might be a concern (again, depending on your devices and UDP settings) and a possible cause for registration issues that persist even after internet access has been established, requiring the ATA to be rebooted afterwards in order for registration to work again. I was explaining what to look out for. In other words, I was trying to give you a heads-up. If the problem doesn't occur for you, great.

[Liptonbrisk]

Also, on a side note, regarding the HT802v2, I've tried to save the entire Device Configuration from the "Download" option but all it does is store it in some "si" file, -"si" being a "system information" file without a file extension?, except that's it's basically unreadable

That's a support/system information package meant for diagnostics--not a configuration report for reading or printing.

I see, based on the admin guide, that the readable export is the plain text “Download Device Configuration” (.txt) with parameter IDs, while the XML backup export is for provisioning/restore and can be encrypted. There is no PDF or JPG export option in the V2 interface. The long alphanumeric entries in the XML are Grandstream P-values, which require a parameter map to interpret rather than being meant for direct reading.

"Download Device Configuration -- Downloads Device Configuration in .txt format."
https://documentation.grandstream.com/k ... ion-guide/

I can't see the UI, but you can look for a page with a “Download Device Configuration” option to obtain a .txt file. That should provide a readable export and list settings by P-value IDs with their configured values. I would guess, navigate to Web UI--> Maintenance ---> Upgrade, and then scroll to the Download section and click “Download Device Configuration” to save the .txt file. However, the contents are formatted for machine interpretation rather than for easy reading. You can download the configuration template from the Tools page on Grandstream's official support website: https://www.grandstream.com/support/tools. You would need the Configuration Template (download the file package). Then look for your ATA model within it. Each P value has a corresponding setting.

Anyway, that's probably not what you want.

and I can't seem to save it into a "pdf" or "jpg" inage file, ... ?

You could try printing the web user interface to PDF: https://www.wikihow.com/Print-to-PDF. However, that typically only captures a single screen at a time. You could try to find a free utility to merge the PDFs together (I've heard of PDFgear). Or you could capture screenshots and paste/import them into a program to create the pdf.

There are plugins and browser extensions that claim to make this process easier, but many of them aren't free. For example, Fireshot has been mentioned to me before. I don't know if it's safe (it might be; I have no idea since I've never used it), and I see the pro version of Fireshot isn't free (the free version only supports single-page PDFs).

The "xml" file from another optional export setting simply exports it to a very long list of alphanumeric numbers that don't really mean anything.

That's for backing up and restoring configuration settings to the ATA.