Grandstream HT801: does it support call forwarding/divert?

I asked this question about the Grandstream HT801 over in the VoIP sub-forum but lack of familiarity with the Hyperoptic VoIP service seems to have caused it to lose focus!

I'm interested in swapping out the Hyperoptic Hub with a third party router without VoIP support, but still want to keep my landline which I've ported to Hyperoptic. My DECT phone recently got fried by a power surge, and so I currently forward all calls to the landline to my mobile phone, which actually woks very well (to the point where I'm not planning on installing a replacement landline phone).

Does anyone know if the HT801 when connected to the Hyperoptic service (through a third party router) will support call forward/divert (with caller id etc. etc.) in the same way as the Hyperoptic Hub?

Many thanks!

I use a Gigaset CL750A with a third party router, and caller ID is fine. Never tried call divert as I never use my landline but I can't see any reason why it wouldn't work as long as the option is in the menu?

Once you get your SIP settings from Hyperoptic, you could just set it up on your mobile as a SIP account and not have to do the divert.

Edited by locutus (Mon 24-May-21 09:04:23)

In reply to a post by Milhouse:

I asked this question about the Grandstream HT801 over in the VoIP sub-forum but lack of familiarity with the Hyperoptic VoIP service seems to have caused it to lose focus!

I'm interested in swapping out the Hyperoptic Hub with a third party router without VoIP support, but still want to keep my landline which I've ported to Hyperoptic. My DECT phone recently got fried by a power surge, and so I currently forward all calls to the landline to my mobile phone, which actually woks very well (to the point where I'm not planning on installing a replacement landline phone).

Does anyone know if the HT801 when connected to the Hyperoptic service (through a third party router) will support call forward/divert (with caller id etc. etc.) in the same way as the Hyperoptic Hub?

Many thanks!

As you don't plan on having a phone connected, it may be worth asking if Hyperoptic can just forward all calls to your mobile from their end.

Thanks
Dan

In reply to a post by locutus:

Once you get your SIP settings from Hyperoptic, you could just set it up on your mobile as a SIP account and not have to do the divert.

While waiting for a HT801 to arrive I have been trying to use Acrobit Softphone which is a possible solution (no extra hardware, cheaper calls as there's no additional forwarding cost to mobile etc.) but there's a problem receiving the incoming call push notifications to my Android 10 phone from the Acrobit SIPIS server because (according to Acrobit Support) Hyperoptic appear to be blocking the IP addresses that the Acrobit SIPIS server is using to register my account.

https://faq.acrobits.net/about-push-notifications

I went on chat to Hyperoptic yesterday where I was told they don't block any IP addresses, which I relayed to Acrobits Support who ran tests from their end and they have now confirmed their IP addresses ARE being blocked by Hyperoptic, so possibly the Hyperoptic person I chatted with didn't quite understand the issue.

I'm guessing that Hyperoptic only permit registrations to the SIP server from their own Hyperoptic IP address range, and block all non-Hyperoptic IP addresses.

To confirm this, I tried to make a call with Acrobits Softphone over a cellular connection, and that also now fails, presumably as I'm no longer able to register from a non-Hyperoptic IP address (I'm using 3 UK).

I can make calls from Acrobit Softphone without a problem over WiFi (when connected to my Hyperoptic Hub) so it looks like Hyperoptic have locked down their SIP server to only accepts registrations from their own IP address range, which likely means the Hyperoptic SIP server is not going to be compatible with anyone wanting to use a mobile VoIP client.

This is the reply from Acrobits Support:

Unfortunately, it is like I thought. We send register request, but get no response from them. SIPIS is behind neither a firewall or NAT so it won't be some network issue on our side. I still think it is some blocking on their side most likely (maybe unintentional) and they need to take a closer look.

I can add that the issue is specifically from
159.65.186.176
right now, though as I said, we could potentially register from any of those IPs I sent.
159.65.186.176
159.65.251.173
159.65.252.186
159.65.253.49
165.227.184.188
167.99.48.91
167.99.119.203
167.99.119.244

Hopefully someone from Hyperoptic CS can see this and tell me what is going on and is able to resolve the issue (if not, then I guess Hyperoptic VoIP is going to be permanently incompatible with Acrobits Softphone, and possibly many others).

Just had another chat on the Hyperoptic web site and the Hyperoptic CS are adamant they don't block IP addresses to the SIP server, yet it doesn't appear possible to register with sip.hyperoptic.com from a non-Hyperoptic IP address.

They've asked if the Acrobits tech support can call them, so hopefully we can make progress that way otherwise I think the Hyperoptic VoIP service will be limited to registrations only from the Hyperoptic network (which will be very limiting for users of mobile devices).

Oh well if all else fails there's always the HT801 (and additional call costs for the forwarded calls).

Acrobits have reached out to Hyperoptic support by email (ironically, Acrobits "don't do phone support"!), so let's see how that goes, but I'm more than happy to discuss this here with Hyperoptic CS as well!

Acrobits have provided me with a test Python script (it contains some private credentials so I won't be posting it - I can provide it to Hyperoptics CS if needed) which connects to the Hyperoptic SIP server, what follows are screenshots of the different responses when run on Hyperoptic and non-Hyperoptic networks..

First, from a Raspberry PI running on the Hyperoptic LAN/WAN:

Hyperoptic SIP on Hyperoptic LAN

And then the same script, this time on a FreeBSD server running on a Sky (UK) network:

Hyperoptic SIP on Sky LAN

This is not in any way conclusive, but it does demonstrate that it is possible to get a response from the Hyperoptic SIP server when connecting from the Hyperoptic network, and that there is no response when making the same connection from a non-Hyperoptic network (Sky, cellular etc.). The Acrobits SIPIS server is not behind a firewall or NAT, but is located in the US, although it's unlikely that geographical location is a factor here.

I'm guessing this blocking (or lack of response) is indeed intentional, perhaps as some sort of "security" measure, but it significantly reduces the usefulness of the Hyperoptic VoIP offering. It could also be an unintentional misconfiguration, which is why nobody at Hyperoptic seems to be aware of any issues when connecting from non-Hyperoptic networks.

At the very least it would be good to get to the bottom of this and either have it confirmed that registrations from non-Hyperoptic networks are NOT allowed, or have the problem resolved so that it is possible to register from non-Hyperoptic networks.

Not sure how it's meant to work but the visible parts don't appear to show a connection to port 5060 but rather a dynamic high port.

The only mention of port 5060 in that output is response to the DNS SRV lookup.

My hunch would be that you wouldn't get a responses flowing for the additional UDP media traffic ports until the SIP registration / authentication succeeds on port 5060, at least from the outside.

Hyperoptic might not be so worried about random port scanning from inside their own network (but I would be).

However I understand why you would redact some output and not want to show the script either.

Edited by prlzx (Thu 27-May-21 18:44:51)

In reply to a post by prlzx:

Not sure how it's meant to work but the visible parts don't appear to show a connection to port 5060 but rather a dynamic high port.

The only mention of port 5060 in that output is response to the DNS SRV lookup.

That's probably because the test script is using a "conversation" gleaned from a log I previously provided to Acrobits from my phone, so some of the information in the SIP server response may not be entirely accurate, however I think the point is that there is no response whatsoever when trying to communicate over the Sky network, but you do get a response (even if it's garbage, or just plain echo) from from the Hyperoptic network.

OK here's a redacted version of the test script that should still work (ie. you'll get a response when run over the Hyperoptic network, and no response from a non-Hyperoptic network):

sip.py (pastebin)

If anyone tries it, let us know how you get on!

Indeed, apologies but it doesn't seem to work does it. I just tried it. Fine on wifi on my mobile phone, but won't register when on Vodafone.