Kitz Forum
Broadband Related => Voice over IP (VoIP) => Topic started by: broadstairs on October 24, 2021, 04:44:56 PM
-
I thought it would be interesting to know what people here with VOIP use for their connection. What ATAs do folks use for their analog phones? Do you use a dedicated VOIP phone? What issues have people had which made life difficult with VOIP?
Stuart
-
I currently use a Fritzbox 7490 as a DECT base station which connects to my Firebrick 2900, which finally connects to either Flextel or AAISP. I have BT handsets.
A long time ago I had a difficulty getting the BT handsets to work on the Fritzbox 7490 DECT base station, but with some experimentation of the settings I eventually found out what worked and what didn't.
I also use Flextel for the fact that it can generally mostly reveal what an incoming hidden/private number is (except the last three digits) as well as offer the option to block the actual number that Flextel saw in full. I also have a call screening system setup on it so that the caller has to press a number to get through to me.
-
I've had very good experience for many years with the Gigaset IP DECT phones - firstly the C475IP, and currently the N300IP.
The base station lets you register up to 6 VOIP accounts, as well as a single analogue line, and then you configure which lines your different handsets use for incoming/outgoing calls.
-
Cisco 2 Port ATA cheap and easy to setup ATA192
-
I've this week setup a Gigaset N300 IP system. Works nicely and very impressed with it. Not expensive for what it does.
I've also run Voip through a number of Draytek V model routers in recent years, and that works well. Sometimes took a bit of work to get the configs right.
Also I ran a number of Linksys ATA units, like the PAP2 series, for a few years. Again those worked well. Although getting the configs right took a lot of time, especially at first. Yes those were cheap.
-
I've still got a SIPgate account which I haven't used since I retired. When I got the Fritz!box 7530 from Zen I saw it had the capability of SIP. So I gave it a go, plugged in a corded handset, followed these instructions (https://basichelp.sipgate.co.uk/hc/en-gb/articles/206981409-AVM-FRITZ-Box-All-models) and it worked straight off.
-
Grandstream WP820
Yealink W60
Yealink T19
Fanvil X4
Cisco Sipura SPA122
Think that's all I'm using at present
-
I am investigating a Grandstream HT801 as a means to continue to use my existing telephones . . .
-
Gigaset N300IP here too, I haven't used the VoIP functionality other than to test it works (though I do have two active accounts on it) but its my DECT base station for the landline and replaced all the old failing BT handsets with Gigaset C430HX units. So once FTTP is available, the transition should be smooth.
The important thing is my mum is already used to the handsets now so she wont notice the difference when the time comes.
-
I'm using Fritzbox 7530 for Voip and answerphone with my existing DECT basestation & handsets, connected through A & A Voip service. Works prefectly.
-
I have Grandstream GXP2170 which is use regularly as my 'office' phone together with a SIPgate account. I also have a Grandstream HT 802.2 which I planned to use to convert the house phones at some point which I have yet to set up.
I started using the VOIP stuff as a test / experiment and it has worked very well.
The Grandstream stuff seems good value and works well, although setup was not exactly uncomplicated in my case.
-
Hi all,
I am newly registered to the board but have been lurking for a while.
I use a Grandstream HT812 ATA and have it working on Sipgate Basic.
I bought a BT DECT phone to use with it, so that I can try out how I will need to my migrate my existing DECT phones in the future.
Cheers,
Tony
-
We use a Gigaset N300A as well, originally because it was compatible with our two existing DEC handsets. However starting from scratch I don't really see the point of DECT, I would look for a self contained wireless handset. We use the landline a lot less nowadays as we now have mobile coverage at home, so don't need two handsets either.
-
There's good reason to use DECT, WiFi is prone to jitter and packet loss, its not optimal for any low latency protocol where you want reliable delivery. DECT on the other hand is optimised for its job and uses a much lower frequency so the range is far better too.
Plus having it all managed by a single base station its easier to route calls, have different handsets for different numbers, a single point to manage all the handsets and not needing every handset to have its own connection to the VoIP server so managing NAT traversal is less hassle.
-
I have a Polycom Spectralink 8020, which are now obsolete I believe, which was a right PITA to set up. It was extremely fiddly inputting the WiFi SSID and password using the handset keys on the small LCD screen. The SIP server details and user information had to be held on a TFTP server which was an adventure in itself! However, once set up it works extremely well. Presumably the modern-day equivalents are much easier to configure.
-
Yealink W60P with a total of 3 handsets. Don't get very many calls but the handsets are good to use as intercoms in the house.
Connected to Sipgate with two numbers over IPv6 (no NAT keepalives or STUN servers required anymore).
-
Frustrating Gigaset haven't added IPv6 to the N300.
-
Connected to Sipgate with two numbers over IPv6 (no NAT keepalives or STUN servers required anymore).
Can you clarify on the keepalives? Normally these are needed not just for NAT but to keep alive the permissions in the firewall. Of course it depends on your firewall, however in most installations the action of a host inside your network sending data out to the Internet, causes the firewall to permit inbound packets representing replies. In the case of UDP these rules normally timeout fairly quickly, hence the need to the SIP endpoint to keep them alive with Options ping or similar. Do you have a static inbound permission on your firewall?
-
Indeed they would also keep a firewall state open, however with Sipgate on IPv6, incoming signalling for calls on port 5060 can arrive from several different IPv6 servers with different addresses, so keepalives anyway are not reliable on IPv6 with Sipgate, as the firewall will only allow in packets from the original IPv6 address that is 'keeping alive' the firewall state. To make it all work, I simply have a firewall rule that allows all traffic in from Sipgate's IPv6 range (2001:ab7::/32), therefore no keepalives.